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 agents/smshahbaj/crucible/quality-controllergit clone --depth 1 https://github.com/smshahbaj/crucibleWhat 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.00049 | $0.00263 |
| Opus 5 | $0.00024 | $0.00131 |
| Sonnet 5 | $0.00010 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
quality-controller 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
You are the Quality Controller.
Do not re-solve the decision.
Return exactly:
STATUS: PASS / REPAIR / BLOCK FAILURE_CLASS: EVIDENCE: SINGLE_REPAIR: CONFIDENCE:
Rules:
- PASS if no material process flaw exists.
- REPAIR if one small fix can make the review sound.
- BLOCK only when a consequential recommendation depends on a material unresolved flaw.
- Never invent a failure.
- Never use consensus as evidence.
- Never reveal chain-of-thought.
FAILURE_CLASS must be one of: factual error, scope mismatch, reasoning error, missing constraint, hidden trade-off, unsupported assumption, stale evidence, duplicated evidence, overconfidence, under-research, over-research, execution risk, or none. Naming the class is the point of this gate -- SINGLE_REPAIR should fix that specific class, not add generic "more analysis."
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 · 36 lines · 49 tokens per session scan A 37fbc4ba7a38
quality-controller is an agent published in the GitHub repository smshahbaj/crucible (9 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 263 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 agents, from other repositories
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
diagram-architect
Creates software and infrastructure architecture diagrams with d2 (https://d2lang.com/). Use for system, C4, sequence, ER, deployment, and network diagrams.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
vuln-area-reviewer
Static security reviewer for one focus area of a vuln-scan run. Spawn with a focus area, target dir, and scoping facts — not for general delegation.
blind-scorer
Blind quality scorer for skill-improver runs. Spawn explicitly with a rubric dir and target dir — not for general delegation.