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 skills add supportersimulator/3-surgeons --skill quality-gatesgit clone --depth 1 https://github.com/supportersimulator/3-surgeonsWrote 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/skills/supportersimulator/3-surgeons/quality-gates)<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/quality-gates"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/quality-gates/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/skills/supportersimulator/3-surgeons/quality-gates"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/quality-gates.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.00025 | $0.01583 |
| Opus 5 | $0.00013 | $0.00792 |
| Sonnet 5 | $0.00005 | $0.00317 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade C, and why
quality-gates scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| **No destructive operations** | `drop database`, `truncate table`, `delete all prod data`, `rm -rf /`, `wipe all data`, `destroy database` | How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Gates
Three Gate Types
The 3-Surgeons system provides three quality gates, each serving a different purpose:
| Gate | Purpose | When to Run |
|---|---|---|
| GainsGate | Infrastructure health verification | Between major phases, after deployments |
| CardioGate | Quality review chain with rate limiting | When quality degradation is detected |
| CorrigibilityGate | Safety invariant enforcement | Before destructive or risky actions |
GainsGate
When to Run
- Between major phases -- after completing phase A, run gains-gate before starting phase B
- After deployments -- verify the system is healthy post-deploy
- After infrastructure changes -- new config, restarted services, changed endpoints
- Before long-running operations -- ensure everything is healthy before committing to a multi-step process
How to Invoke
CLI
3s gains-gate
MCP Tool
gains_gate()
Default Checks
| Check | Critical? | What It Verifies |
|---|---|---|
neurologist_health |
No | Pings Neurologist endpoint. Local model may be offline. |
cardiologist_health |
No | Pings Cardiologist endpoint. API may be unavailable. |
evidence_store |
Yes | Evidence DB is accessible and queryable. |
state_backend |
Yes | State backend responds to ping. |
Gate Pass/Fail Logic
The gate passes only if all critical checks pass. Non-critical failures are recorded but do not block progress.
- All critical checks pass + some non-critical fail = PASS (with warnings)
- Any critical check fails = FAIL (must fix before proceeding)
Interpreting Results
Running gains gate...
[PASS] neurologist_health: Neurologist operational (89ms)
[FAIL] cardiologist_health: Cardiologist unreachable: Connection refused
[PASS][critical] evidence_store: Evidence store accessible (42 learnings)
[PASS][critical] state_backend: State backend operational
PASS: 3/4 checks passed (non-critical failures: cardiologist_health) (23ms)
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.
- 8d ago First seen · 187 lines · 25 tokens per session scan C ccfa8a7b8ca6
quality-gates is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,583 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
cherry-pr-test
Test Cherry Studio PRs by resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch.
visual-acceptance
A visual final-review method for user-interface changes. It checks the rendered result with repeatable screenshots, pixel values, computed styles, and CSS layering checks across themes.
ultra-adlc
End-to-end delivery orchestration for explicitly requested, very large software changes that must be completely implemented and independently proven. Use when the user invokes "ultra-adlc" or asks for an Ultra-ADLC-scale full delivery; do not use for ordinary features, small fixes, reviews, or ad hoc parallel work.
superpowers-test-driven-development
Writing or fixing any code? Load first — write the failing test before the code.
diagnosing-bugs
Use when debugging a bug, test failure, or unexpected behavior, before proposing fixes. Build a tight red-capable feedback loop first, then reproduce, hypothesise, instrument, fix, and clean up.