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 integrity-checkgit 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/integrity-check)<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/integrity-check"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/integrity-check.svg" alt="Measured on agentmods" 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.00020 | $0.00351 |
| Opus 5 | $0.00010 | $0.00176 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
integrity-check 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 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.
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
Integrity Check
The CorrigibilityGate's integrity verification mode. Detects state corruption, counter tampering, and service degradation.
When to Use
- After a crash or unexpected restart
- When state values seem inconsistent
- After manual state modifications
- Periodic health verification (beyond what gains-gate checks)
What It Checks
- Monotonic counters — event counts should only increase. A decrease signals data loss or tampering.
- Service health — state backend is responding to pings.
- Evidence operational — evidence store can be queried.
How It Works
The integrity check reads integrity:* keys from the state backend:
integrity:events_countvsintegrity:events_count:prev- If current < previous → something decreased a counter → FAIL
Without a state backend, integrity checks are skipped (passes with "skipped" message).
Output
Standard GateResult:
passed— true if all checks passchecks— individual check results with names and messagesduration_ms— how long the check took
Relationship to Other Gates
| Gate | Purpose | When |
|---|---|---|
| GainsGate | Infrastructure health | Between phases |
| CardioGate | Quality review + rate limit | Automated quality checks |
| CorrigibilityGate.run() | Text safety (regex) | Before destructive ops |
| CorrigibilityGate.check_integrity() | Structural integrity | After crashes, periodic |
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 · 46 lines · 20 tokens per session scan A f59e693019d2
integrity-check is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 351 once invoked, about $0.0001 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 skills, from other repositories
cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance…
cherry-assistant-guide
A guide for looking up Cherry Studio's product details and diagnosing problems such as connection failures, setup errors, and runtime issues.
cherry-studio-feedback
A guide for handling Cherry Studio bug reports, interface problems, user-experience issues, and feature suggestions.
fastgpt-docker-deploy
FastGPT Docker Compose self-hosting deployment workflow. Use when a user asks an AI agent to deploy FastGPT with Docker by referencing /deploy/SKILL.md, including creating an empty fastgpt directory, running the install script in non-interactive mode, starting Docker Compose, monitoring service health, troubleshooting…
ai4j-app-builder
Use this skill when helping users build applications with AI4J in their own Java or Spring Boot projects, including first chat, streaming, tool/function calls, MCP, RAG, memory, Agent runtime, Coding Agent CLI embedding, FlowGram integration, provider configuration, dependency selection, and troubleshooting. It guides…
superpowers-systematic-debugging
Any bug, failing or flaky test, or surprise behavior? Load BEFORE you investigate or guess.