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 ai-driven-dev/framework --skill 01-acceptance-qagit clone --depth 1 https://github.com/ai-driven-dev/frameworkWrote 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/ai-driven-dev/framework/01-acceptance-qa)<a href="https://agentmods.dev/skills/ai-driven-dev/framework/01-acceptance-qa"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/01-acceptance-qa/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/ai-driven-dev/framework/01-acceptance-qa"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/01-acceptance-qa.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.00059 | $0.00357 |
| Opus 5.5 | $0.00024 | $0.00143 |
| Sonnet 5.5 | $0.00012 | $0.00071 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
01-acceptance-qa 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 21d 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 QA
flowchart LR
scope["load-scope"] --> prerequisites["prerequisites"] --> prepare["prepare-run"] --> run["run-scenarios"] --> report["qa.md"]
scope -- skipped --> report
Actions
Read only the next action's file before running it.
| # | Action | Does |
|---|---|---|
| 01 | load-scope |
Lock at most one happy path and the edge cases its acceptance criteria name |
| 02 | prerequisites |
Verify the browser runner and media dependencies |
| 03 | prepare-run |
Resolve the shortest deterministic path to executable runs |
| 04 | run-scenarios |
Record, normalize, verify, reset, and report every scenario |
Transversal rules
- Run against a reviewed change and never patch the application.
- Never delete data not proven test-only.
- Never derive a scenario from the diff or the source code; every scenario traces to an acceptance criterion.
- Never spawn agents. Batch independent reads and tool checks, but keep state-changing browser work sequential.
- Do not narrate action transitions, searches, fixtures, selectors, or successful checks. Report only a blocker, a required decision, or the final verdict and paths.
What ships with it
6 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.
- 21d ago First seen · 33 lines · 59 tokens per session scan A bf78facee83d
01-acceptance-qa is a skill published in the GitHub repository ai-driven-dev/framework (518 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 357 once invoked, about $0.0002 per session on Opus 5.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-09-25.
Other skills, from other repositories
agent-evaluation
A guide to measuring whether an AI agent works reliably on the tasks that matter. It covers repeatable test environments, program checks, human-like scoring rules, failure analysis, and experiments that separate model problems from system problems.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
game-playtesting
Test a game end to end like a player across boot, controls, gameplay loops, UI, save state, failure recovery, rendering, audio, performance, and platform behavior. Use after game implementation or for regression investigation.
browser-qa
Validate web applications through the embedded browser with responsive, interaction, console, and screenshot checks.
starfleetctl-dev
Developing and deploying the starfleetctl source itself — claim protocol, make, bootstrap, daemon restarts in the right order, end-to-end verification. Load before editing anything in a starfleetctl source checkout, before running starfleet-bootstrap, or when a web/plugin change 'is done' but the fleet does not see it.