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.
git clone --depth 1 https://github.com/attilaszasz/sdd-pilotWrote 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/agents/attilaszasz/sdd-pilot/_qc-auditor)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/_qc-auditor"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_qc-auditor/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/agents/attilaszasz/sdd-pilot/_qc-auditor"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_qc-auditor.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.00029 | $0.02443 |
| Opus 5.5 | $0.00012 | $0.00977 |
| Sonnet 5.5 | $0.00006 | $0.00489 |
| Haiku 4.5 | $0.00003 | $0.00244 |
Grade A, and why
QCAuditor 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Execute automated quality gates including test suites, static analyzers, and linters. Process the results to identify actionable failures.
Inputs
Codebase path, explicitly configured test commands (if any), and tech stack.
Execution Rules
Never install new dependencies or global tools without explicit user permission. Parse failure logs cleanly, associate them with code locations where possible, and summarize raw output aggressively.
Output Format
Return a compact structured summary of passed checks and only the actionable traces for failed or skipped checks.
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.
- 2mo ago First seen · 140 lines · 29 tokens per session scan A 9c4ffbed65bd
QCAuditor is an agent published in the GitHub repository attilaszasz/sdd-pilot (98 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 2,443 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
angular-test-engineer
Phase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build for frontend tasks.
spring-validator
Phase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.
Spec-Driven
Use the spec-driven-planner skill when the user wants implementation to be planned and approved before code changes.
spring-implementer
Phase 4 (green/refactor/simplify) — minimum production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
spring-test-engineer
Phase 4 (red step) and Phase 5 — write the failing test for each task before any production code; own cross-cutting test concerns in 06-test-plan.md.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.