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/validategit 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.00036 | $0.01366 |
| Opus 5 | $0.00018 | $0.00683 |
| Sonnet 5 | $0.00007 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
validate 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.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Compliance Check
Perform a comprehensive compliance check of the current project against SDLC requirements.
Process
1. Detect Project Type
First, identify the project's language and framework:
# Check for language indicators
ls Cargo.toml package.json pyproject.toml pom.xml build.gradle go.mod 2>/dev/null
2. Run Domain Checks
Check each SDLC domain for compliance. Use the specialized agents if available, or perform checks directly.
Build System Check
- Makefile exists with standard targets
- Build configuration present
-
make buildworks -
make testworks -
make lintworks -
make formatworks
# Verify Makefile targets
make -n build test lint format clean 2>/dev/null && echo "✓ Makefile targets OK" || echo "✗ Makefile missing targets"
Code Quality Check
- Formatter configured
- Linter configured
- Format check passes
- Lint check passes
# Run format check
make format-check 2>/dev/null || echo "Format check failed or not configured"
# Run lint
make lint 2>/dev/null || echo "Lint failed or not configured"
Testing Check
- Tests exist
- Tests pass
- Coverage configured
# Run tests
make test 2>/dev/null || echo "Tests failed or not configured"
CI/CD Check
- Workflow file exists
- Required jobs present
- Actions pinned
- Caching configured
# Check CI workflow
ls .github/workflows/ci.yml .github/workflows/ci.yaml 2>/dev/null || echo "✗ No CI workflow found"
# Check for pinned actions
grep -E "uses:.*@v[0-9]" .github/workflows/*.yml 2>/dev/null | head -5
Security Check
- Vulnerability scanning configured
- License compliance defined
- SECURITY.md exists
# Check security config
ls SECURITY.md 2>/dev/null || echo "✗ SECURITY.md missing"
ls cargo-deny.toml .cargo/audit.toml 2>/dev/null # Rust
ls .npmrc package.json 2>/dev/null | xargs grep -l "audit" 2>/dev/null # Node
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 · 221 lines · 36 tokens per session scan A 4b3e3639c584
validate is a command published in the GitHub repository zircote-plugins/sdlc-quality (10 stars, last pushed 29d ago), licensed MIT. It adds 36 tokens to every session and 1,366 once invoked, about $0.0002 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
review
Review staged git changes for issues before committing.
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
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.
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.
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.