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 agentmods add skills/xrensiu/claude-code-forge/acceptance-fleetnpx skills add XRenSiu/claude-code-forge --skill acceptance-fleetgit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/acceptance-fleet)<a href="https://agentmods.dev/skills/xrensiu/claude-code-forge/acceptance-fleet"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/acceptance-fleet.svg" alt="Measured on agentmods" 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 | $0.00335 | $0.05294 |
| Opus 5 | $0.00168 | $0.02647 |
| Sonnet 5 | $0.00067 | $0.01059 |
| Haiku 4.5 | $0.00034 | $0.00529 |
Grade C, and why
acceptance-fleet scanned grade C with 1 finding 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 4d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- **Missing `spec-robustness.md`** — do NOT refuse; proceed with a warning that S2.5 was skipped and `/spec-gaming-detector` runs in max-suspicion mode (its own iron rule 10 activates). How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
acceptance-fleet — Step 5-6 orchestrator (v1.0+ pure dispatch)
You are invoked to verify an implementation against a done_when.yaml contract by dispatching the 6 standalone review skills, synthesizing their findings via /meta-judge, and decoding the verdict into a four-state ratchet decision (DONE / FIX / SPEC_DRIFT / GAMING_RISK).
Say once at the start, then start working:
"I'm using the acceptance-fleet skill. I'll dispatch the 6 review skills in parallel against your impl, hand findings to /meta-judge, decode the verdict into the 4-state ratchet, and write a full ratchet-log/iteration-NNN/ trace."
Do not narrate further — just walk the phases.
What changed in v1.0.0 (read this once if migrating from v0.x)
| v0.x (monolithic fleet) | v1.0+ (orchestrator) |
|---|---|
| 7 evaluator roles embedded internally (test-runner / existence-checker / requirement-tracer / design-reviewer / adversarial-reviewer / edge-case-hunter / e2e-explorer) | 6 standalone skills dispatched: /code-reviewer × focuses, /qa-reviewer, /pm-reviewer, /spec-drift-detector, /spec-gaming-detector |
| Meta-judge was a fleet phase (S3) | /meta-judge is its own skill, invoked by this orchestrator |
references/role-prompts.md carried all 8 role prompts |
Each review skill owns its prompt + references; orchestrator just calls them |
references/finding-schema.yaml had all schemas |
Each review skill owns its own finding-schema.yaml; meta-judge owns the final-verdict schema |
gaming-detector-patterns.md, meta-judge-protocol.md lived in this skill |
Migrated to spec-gaming-detector and meta-judge respectively |
done_when.yaml had a fitness: layer |
Retired per HTML v2 §3.5; replaced with rules: layer consumed by /meta-judge |
If you have v0.x ratchet-log/ directories, they remain readable — the new orchestrator writes the same format under references/ratchet-log-format.md. The migration is at the skill definition level, not the artifact level.
What ships with it
4 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.
- 4d ago First seen · 317 lines · 335 tokens per session scan C a542c960c0d2
acceptance-fleet is a skill published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 2mo ago), licensed MIT. It adds 335 tokens to every session and 5,294 once invoked, about $0.0017 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…