Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add jeremylongworth-source/AgentSkills --skill acceptance-criteria-mappergit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jeremylongworth-source/agentskills/acceptance-criteria-mapper)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/acceptance-criteria-mapper"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/acceptance-criteria-mapper/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/acceptance-criteria-mapper"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/acceptance-criteria-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00295 |
| Opus 5 | $0.00024 | $0.00148 |
| Sonnet 5 | $0.00010 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
acceptance-criteria-mapper scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Acceptance Criteria Mapper
Core Workflow
- Identify the artifact, audience, and decision the criteria must support.
- Convert broad goals into observable pass/fail checks.
- Separate required behavior, optional quality signals, and out-of-scope expectations.
- Add evidence requirements for each criterion: file, output, test, reviewer note, citation, trace, or command result.
- Include safety and refusal criteria for high-risk workflows.
- Flag criteria that are too subjective, too broad, or dependent on private data.
Safety Rules
- Do not convert legal, financial, medical, security, or employment judgment into automatic approval criteria.
- Do not mark criteria satisfied without evidence.
- Do not use vague criteria such as "looks good" without observable checks.
Deliverable Shape
For criteria maps, provide:
- Artifact and audience
- Required acceptance criteria
- Optional quality criteria
- Evidence required
- Safety/refusal criteria
- Open assumptions
- Validation method
References
- Read
references/acceptance-criteria-mapper-checklist.mdwhen turning goals into measurable checks.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 44 lines · 49 tokens per session scan A 6b85b3071cb4
acceptance-criteria-mapper is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 295 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
i4h-catheter-navigation-render-drr
Render a single DRR fluoroscopy frame from a CT cache or synthetic phantom. Use when asked to render DRR, generate a fluoro image, or smoke-test the Slang renderer.