agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/compliance-audit/control-testing-sampling/SKILL.md

control-testing-sampling

Skill0 starsChanged 11 days agoMITView on GitHub

Test security controls for design and operating effectiveness — test of design vs. operating effectiveness, attribute sampling with sample sizes by control frequency, random selection, exception evaluation and deficiency classification — for internal audit, SOX ITGC, SOC 2 readiness or second-line assurance. Use when planning control tests, choosing sample sizes, or evaluating exceptions found in testing.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document population source, count, selection method and seed.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Control Testing and Sampling

Design vs. operation

  • Test of design (TOD): walkthrough of one instance — if performed as described, would the control prevent/detect the risk?
  • Test of operating effectiveness (TOE): did it operate consistently over the period? Requires sampling.

Common sample size guidance (attribute testing, low expected deviation)

Control frequencyPopulation/periodTypical sample
Annual11
Quarterly42
Monthly122–5
Weekly525–15
Daily~250–36520–40
Multiple times per day / transactional> 36525–60
Automated (system-enforced)—1 per configuration + change management test

Firms use different tables — follow your audit methodology; these ranges reflect widely used practice.

Random selection (reproducible)

import csv, random
rows = list(csv.DictReader(open("population.csv")))
random.seed(20261031)                    # record the seed in workpapers
sample = random.sample(rows, k=25)

Document population source, count, selection method and seed.

Evaluate exceptions

  1. Confirm it's a true exception (not a misunderstanding of the control).
  2. Root cause and whether it's isolated or systemic; consider expanding sample.
  3. Compensating controls?
  4. Classify: control deficiency / significant deficiency / material weakness (SOX), or nonconformity minor/major (ISO).
  5. Remediation plan and retest.

Workpaper fields

Control | Risk | Test procedure | Population (source, count) | Sample (method, size) | Attributes tested | Results | Exceptions | Conclusion | Tester/reviewer/date

Related skills

audit-evidence-package, control-mapping, segregation-of-duties

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.