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 IgorGanapolsky/ThumbGate --skill thumbgate-doctorgit clone --depth 1 https://github.com/IgorGanapolsky/ThumbGateWrote 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/igorganapolsky/thumbgate/thumbgate-doctor)<a href="https://agentmods.dev/skills/igorganapolsky/thumbgate/thumbgate-doctor"><img src="https://agentmods.dev/badge/skills/igorganapolsky/thumbgate/thumbgate-doctor/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/igorganapolsky/thumbgate/thumbgate-doctor"><img src="https://agentmods.dev/badge/skills/igorganapolsky/thumbgate/thumbgate-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 10 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 3 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 19 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 25 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 36 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 38 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 43 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 44 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 48 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 52 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 54 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00168 | $0.00782 |
| Opus 5.5 | $0.00067 | $0.00313 |
| Sonnet 5.5 | $0.00034 | $0.00156 |
| Haiku 4.5 | $0.00017 | $0.00078 |
Grade A, and why
thumbgate-doctor 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ThumbGate Doctor
Audit whether ThumbGate is actually wired into this agent — PreToolUse / SessionStart hooks installed, MCP server reachable, lesson store present, statusline, overall agent-readiness — then tell the user exactly what to fix.
This skill wraps existing ThumbGate capability and adds no new logic — it runs the existing doctor + integrity checks.
Workflow
- Run the wiring/health audit:
(Addnpx thumbgate doctor--jsonfor a machine-readable report.) It exits non-zero when the project is notready. - Verify the runtime path with the
check_operational_integrityMCP tool — this confirms the server-side enforcement path is live, not just the local config. - Summarize: ✅ what's wired (hooks, MCP, store, statusline) and ❌ what's missing, each with
its exact fix command (usually
npx thumbgate init). - Lead with the fix. If everything is green, say so plainly with the readiness status; if not, lead with the single highest-impact fix.
The full readiness checklist (each check, what a failure means, and its fix) is in references/wiring-checklist.md.
Example
Input: "why aren't my gates firing? is ThumbGate even wired up?"
Action: run npx thumbgate doctor, then check_operational_integrity, then:
❌ PreToolUse hook not installed — run
npx thumbgate init. ✅ MCP server reachable. ✅ Lesson store present. Fix the hook and your promoted rules will start blocking.
Troubleshooting
npx thumbgate doctorexits non-zero: that's the point — read which checks failed and apply the printed fix (usuallynpx thumbgate init).- Doctor green but gates still don't fire: the rule may not be active — check the thumbgate-rules skill — or no gated action has been attempted yet — check the thumbgate-blocked skill.
check_operational_integrityunreachable while doctor is green: local config is fine but the MCP server isn't running — restart it (npx thumbgate serve).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 57 lines · 168 tokens per session scan A 6b6e3c3263cc
thumbgate-doctor is a skill published in the GitHub repository IgorGanapolsky/ThumbGate (29 stars, last pushed today), licensed MIT. It adds 168 tokens to every session and 782 once invoked, about $0.0007 per session on Opus 5.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 skills, from other repositories
sodam-loop-repair
A Bash safety rule requiring every Bash call to include a timeout calculated from validation settings, with a stated default of 300000 milliseconds. Bash is a command-line shell used to run scripts and commands.
sodam-loop-status
A self-check command for SoDamLoop, a software system with safety components. It checks whether those components are still working normally.
reporting-shared-defects
Routes a defect found in a shared or supplied artifact (a shared prompt, skill, dependency, model, eval, or template) to the downstream teams, agents, and releases that depend on it, not just a local fix. Use when a discovered defect affects others who consume the same artifact. Do not use for a defect local to your…
responding-to-incidents
Runs a live incident the stabilize-first way — name a commander, separate facts from hypotheses, prefer reversible actions, communicate on a cadence, and drive corrective actions to closure. Use when production is broken, data is at risk, or an agent action caused harm. Do not use for routine non-incident work, or as…
nio-scan
Nio code/skill execution-risk scanner. Use when the user wants to scan a file, repo, directory, or skill for execution risks — e.g. "scan this code for risks", "is this file/plugin dangerous", "check this repo for malicious code", "run nio scan on ". Focused single-purpose skill; for other Nio operations use /nio.
nio-doctor
Nio config validator + connectivity check. Use when the user wants to validate their Nio setup — e.g. "run nio doctor", "is my nio config valid / working", "test my OAuth / external endpoint / LLM connectivity", "why isn't my scorer firing". Focused single-purpose skill; for other Nio operations use /nio.