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/setupgit 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.00032 | $0.01879 |
| Opus 5 | $0.00016 | $0.00940 |
| Sonnet 5 | $0.00006 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
setup 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 yesterday.
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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Project Initialization
Initialize a new project with full SDLC compliance from the start.
Process
1. Detect or Confirm Language
If not specified, detect from existing files or ask:
# Auto-detect language
if [ -f "Cargo.toml" ]; then echo "rust"
elif [ -f "package.json" ]; then echo "typescript"
elif [ -f "pyproject.toml" ] || [ -f "setup.py" ]; then echo "python"
elif [ -f "pom.xml" ] || [ -f "build.gradle" ]; then echo "java"
elif [ -f "go.mod" ]; then echo "go"
else echo "unknown"
fi
2. Create Directory Structure
# Create standard directories
mkdir -p src tests docs docs/adrs .github/workflows
# Language-specific directories
# Rust: src/ already standard
# TypeScript: src/, tests/
# Python: src/{package}/, tests/
# Java: src/main/java/, src/test/java/
# Go: cmd/, internal/, pkg/
3. Create Required Files
README.md
# Project Name
[](...)
[](LICENSE)
Brief project description.
## Installation
```bash
# Installation instructions
```
Quick Start
# Usage example
Documentation
See docs/ for detailed documentation.
Contributing
See CONTRIBUTING.md for guidelines.
License
#### LICENSE (MIT default)
MIT License
Copyright (c) [year] [name]
Permission is hereby granted, free of charge, to any person obtaining a copy ...
#### CONTRIBUTING.md
```markdown
# Contributing
## Development Setup
1. Clone the repository
2. Install dependencies: `make setup`
3. Run tests: `make test`
## Code Style
- Run `make format` before committing
- Ensure `make lint` passes
- Follow existing code patterns
## Pull Request Process
1. Create feature branch from `develop`
2. Make changes with tests
3. Update documentation
4. Submit PR with description
## Commit Messages
Follow Conventional Commits:
- `feat:` New features
- `fix:` Bug fixes
- `docs:` Documentation
- `test:` Tests
- `refactor:` Code restructuring
CHANGELOG.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.
- yesterday First seen · 405 lines · 32 tokens per session scan A 85759f3189e3
setup is a command published in the GitHub repository zircote-plugins/sdlc-quality (10 stars, last pushed 28d ago), licensed MIT. It adds 32 tokens to every session and 1,879 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.
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.
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.
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.