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/benkapner/claude-code-basecamp/quality-gategit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWhat 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.00035 | $0.00175 |
| Opus 5 | $0.00017 | $0.00088 |
| Sonnet 5 | $0.00007 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
quality-gate 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
Quality Gate Command
Use the Skill tool to invoke verification-loop explicitly, then run Phases 1-4 + Phase 6.
If the Skill tool is not available or the skill is not found, run the checks directly (see the verification-loop skill for exact commands per phase).
Phases:
- Environment check
- Type check
- Lint check
- Test suite
- (skip Phase 5 — code review is separate)
- Pre-push security scan + .gitignore audit + pre-commit hooks
Produces a verdict: READY TO PUSH or BLOCKED with reasons.
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 · 20 lines · 35 tokens per session scan A 2ea0ee47e9a3
quality-gate is a command published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 13d ago), licensed MIT. It adds 35 tokens to every session and 175 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-30.
Other commands, from other repositories
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
propagate
Use after editing an upstream doc (PRD/SRS/tech-design/feature-spec) to propagate changes downstream and keep the entire doc chain consistent.
analyze
Use when analyzing a document collection to map themes, find conflicts, gaps, and redundancies — generates landscape analysis report.
review
Use when reviewing spec-forge generated documents for quality, completeness, and consistency — auto-fixes issues if found.
audit
Use when auditing existing project docs for quality, completeness, and code alignment — generates findings report with fix recommendations.
tech-design
Use when writing a tech design, architecture doc, RFC, or design document — follows Google Design Doc format.