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 skills/trustmybot/plugin/tmb_recoverynpx skills add trustmybot/plugin --skill tmb_recoverygit clone --depth 1 https://github.com/trustmybot/pluginWrote 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/trustmybot/plugin/tmb_recovery)<a href="https://agentmods.dev/skills/trustmybot/plugin/tmb_recovery"><img src="https://agentmods.dev/badge/skills/trustmybot/plugin/tmb_recovery.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 | $0.00066 | $0.01494 |
| Opus 5 | $0.00033 | $0.00747 |
| Sonnet 5 | $0.00013 | $0.00299 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
tmb_recovery 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recovery — three failure modes, three responses
Bro keeps the user-visible flow moving on recoverable errors. Each failure class has a deterministic fallback path; the judgment is which class applies.
The bundled script ${CLAUDE_PLUGIN_ROOT}/skills/tmb_recovery/scripts/bro-sqlite-readonly.sh is for §B (trajectory-server unreachable). Invoke it via Bash — use it as a black box, not by reading its source directly.
A. MCP tool returns is_error=true
When any MCP call result has is_error: true or content includes {"error": ...}, the call was wrong — not the doctrine.
Protocol
- Halt the current flow immediately. Treat the failed call as the chain's last.
- Pick one path based on the error class:
- Surface verbatim to the Human and ask how to proceed, OR
- If recoverable AND you know the corrected call, append a note recording the error and the corrected retry, then retry.
Error classification
| Error shape | Meaning | Right response |
|---|---|---|
forbidden |
Bro called a tool scoped to another role. | Reconsider whether the action is bro's responsibility. Change the call signature before retrying. |
validation |
Input didn't match the schema (e.g. malformed branch_id). | Fix the input. Retry with the corrected payload. |
| Constraint failure | DB integrity violation (foreign key, unique). | Surface to Human; usually means a stale or duplicate write attempt. |
no matching deferred tools |
The MCP child process is dead. | Switch to degraded mode (§B). |
B. Trajectory-server unreachable
Two distinct sub-cases — read the additionalContext warning from mcp-health-check.sh at session start to tell which one you have.
B.1 — MCP absent this session
The plugin's MCP server is missing from CC's resolved-plugin list — /reload-plugins and full quit + relaunch won't fix it because CC persists the cached config to disk.
During the failure, bro halts. State-writing tools are unreachable; halt to avoid corrupting the audit trail. Read-only sqlite3 fallback (${CLAUDE_PLUGIN_ROOT}/skills/tmb_recovery/scripts/bro-sqlite-readonly.sh) is still available for emergency reads.
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.
- 3d ago First seen · 83 lines · 66 tokens per session scan A 9d6363295b04
tmb_recovery is a skill published in the GitHub repository trustmybot/plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 1,494 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…