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/zircote-plugins/sdlc-quality/test-reportgit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWhat 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.00010 | $0.00530 |
| Opus 5 | $0.00005 | $0.00265 |
| Sonnet 5 | $0.00002 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
test-report 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 3d 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
Generate Test Report
Create a comprehensive report of test execution results.
Report Generation
if [[ ! -f ".claude/test-state.json" ]]; then
echo "No test results found. Run /run-tests first."
exit 1
fi
"./tests/functional/runner.sh" report --format md
"./tests/functional/runner.sh" report --format md > {{output}}
Otherwise, display in conversation.
Report Format
Markdown
# Test Execution Report
**Generated:** 2024-01-20T15:30:00Z
## Summary
| Status | Count | Percentage |
| --------- | ------ | ---------- |
| Passed | 48 | 90.6% |
| Failed | 3 | 5.7% |
| Skipped | 2 | 3.8% |
| **Total** | **53** | **100%** |
## Failed Tests
### search_empty
**Category:** search
**Description:** Search with no results returns empty message
**Expected:**
- contains: "no results"
**Actual Response:**
> Found 0 matches for query
**Failure:** Missing 'no results'
---
## Passed Tests
<details>
<summary>48 tests passed (click to expand)</summary>
- init_basic
- init_with_recall
- crud_create
- crud_read
...
</details>
## Skipped Tests
- external_api_test (tagged: slow)
- integration_full (depends_on: external_api_test)
Historical Reports
Reports are saved to tests/functional/reports/ by default:
tests/functional/reports/
├── 2024-01-20T15-30-00.md
└── latest.md -> 2024-01-20T15-30-00.md
Access historical reports:
ls tests/functional/reports/
cat tests/functional/reports/latest.md
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.
- 3d ago First seen · 118 lines · 10 tokens per session scan A 4c0c59673b29
test-report is a command published in the GitHub repository zircote-plugins/sdlc-quality (10 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 530 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-31.
Other commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
copilot-leak
Copilot's auto-review escapes: find them since the last look, sanitise them, and turn each one into a lesson.
docs
The documentation report: references, diagrams, drift, API docs, badges, README structure, links, Pages.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.