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 commands/aidlc-io/aidlc/benchmarkgit clone --depth 1 https://github.com/aidlc-io/aidlcWhat 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.00021 | $0.00326 |
| Opus 5 | $0.00010 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
benchmark 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 2d 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
/benchmark — Benchmark
You were invoked as /benchmark <epic> with arguments: $ARGUMENTS (the epic id).
Run the benchmark phase for this epic by following the AIDLC dispatch
procedure exactly as /aidlc <epic> benchmark would:
- Read
docs/epics/<epic>/state.json→pipelineId. - In
.aidlc/workspace.yaml, find that pipeline and itsbenchmarkstep (name/agent===benchmark). Use that step'sagent+skills— never assume; two pipelines can wirebenchmarkdifferently. - If the pipeline has no
benchmarkstep, tell the user this epic's pipeline (<pipelineId>) has nobenchmarkphase, suggest/aidlc <epic>to run the next eligible phase, and stop. - Otherwise load the persona (
.claude/agents/<agent>.md) + skill(s) (.claude/skills/<skill>.md), adopt them (unless the active standard isnone), then follow the structural contract: read state/inputs, write todocs/epics/<epic>/artifacts/BENCHMARK-SUMMARY.md(or the step's declared artifact), and tell the user to click "Mark step done".
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.
- 2d ago First seen · 24 lines · 0 tokens per session scan A 0a10cc8d2767
benchmark is a command published in the GitHub repository aidlc-io/aidlc (58 stars, last pushed 28d ago), licensed MIT. It adds 21 tokens to every session and 326 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.