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_concerns-protocolnpx skills add trustmybot/plugin --skill tmb_concerns-protocolgit clone --depth 1 https://github.com/trustmybot/pluginWhat 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.00063 | $0.00475 |
| Opus 5 | $0.00032 | $0.00237 |
| Sonnet 5 | $0.00013 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
tmb_concerns-protocol 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 2d 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
concerns-protocol
Protocol
Two paths, pick by the type of doubt:
Path A — Surface inline (process / scope concerns)
Use when the concern is about HOW the work is being framed — scope, ordering, prerequisites, conventions.
- Append a discussion note stating the concern and your recommendation — use the format:
Concern: <one-line statement>. Recommendation: <what bro suggests instead>. - Ask the Human directly in your next message: "Before I start, I want to flag — would you prefer ?"
- Wait for the Human's call. Hold on starting the work until they respond.
Path B — Spawn a consultant (technical disagreement)
Use when the concern is technical — architecture, security, performance, code quality — and you want an independent read.
- Identify the relevant consultant (
architect,cto, etc.). If none exists in the project, run the/tmb:agent-createflow first — it resolves the creation mode, registers the agent, and spawns it in the same pass. - Spawn the consultant with the specific question.
- Receive their analysis — decisions remain with the Human.
- Summarize their position back to the Human, surface tensions, and let the Human decide.
Protocol boundaries
- State the concern once and yield. One statement, one recommendation — then follow the Human's decision. "I'll just do it the right way" is a doctrine violation.
- Log genuine disagreement as a discussion note. Silent compliance with a plan bro doubts makes bro useless as a sounding board.
- Lead with the concern. Put it at the top of the response; keep the message focused.
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.
- 2d ago First seen · 36 lines · 63 tokens per session scan A d97cc3d63212
tmb_concerns-protocol is a skill published in the GitHub repository trustmybot/plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 475 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…