tmb_planning SKILL.md skillA
tmb_planning from trustmybot/plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add trustmybot/plugin/tmb_planning@git:20261105.fd408a5Pins git:20261105.fd408a5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- trustmybot/plugin
- Path
skills/tmb_planning/SKILL.md- Versions recorded
- 14
- Latest version
- git:20261105.fd408a5, committed Nov 5, 2026
- First version recorded
- Oct 18, 2026
- Size
- 16,893 bytes
- Repository stars
- 6
- License
- MIT
Bro's code-touching flow — verify world model, triage the requirement (reuse vs build), propose branch, write spec, dispatch SWE, verify on return, atomic-close. Loaded on the first code-touching ask of a session.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Planning — bro's code-touching flow ## 1. Verify the world model `world_model_get(depth=2)` returns the project's directory tree with README-derived summaries. The main checkout shows only merged work — when `unmerged_work` is non-empty, those branch tips are part of the codebase too: read context from and base follow-up work on the newest relevant tip (`task_provision base=<branch_id>`). If the response carries `warning: 'world-model-empty'`, run `scan_run(source='bro_auto_initial')` to build it, then re-read. Zoom-in: `world_model_get(path='src/api', depth=1)`. "Where does X live": `world_model_search(query='X', mode='hybrid')`. ## 2. Triage the requirement With the world model in hand, before you commit to building — two quick questions (judgment, not a research project): 1. **Is it actionable?** Well-defined, testable, in scope? If it's vague hand-waving, surface the gap via `tmb_concerns-protocol` (or an AUQ) and pin it down *before* authoring a spec. 2. **Reuse or build?** Once the requirement is real and we'd build something, prefer reuse over reinventing — check two distinct axes before committing to from-scratch code: …
Read the whole file at its exact version.
How to install
mdr add trustmybot/plugin/tmb_planning@sha256:cfb1d577abe9ebf0The line at the top of this page pins the label git:20261105.fd408a5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_c7jsqkc2qperb6da)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 14 versions of this file, between Oct 18, 2026 and Nov 5, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.fd408a5 latest | 2026-11-05 | fd408a5 | 16,893 B | A | view · diff |
| git:20261105.e930e06 | 2026-11-05 | e930e06 | 16,829 B | A | view · diff |
| git:20261105.7b71ab1 | 2026-11-05 | 7b71ab1 | 16,589 B | A | view · diff |
| git:20261103.9e3953c | 2026-11-03 | 9e3953c | 16,391 B | A | view · diff |
| git:20261102.bbeeee9 | 2026-11-02 | bbeeee9 | 16,341 B | A | view · diff |
| git:20261028.9cc886e | 2026-10-28 | 9cc886e | 16,073 B | A | view · diff |
| git:20261026.b1dee64 | 2026-10-26 | b1dee64 | 15,957 B | A | view · diff |
| git:20261026.cb1f627 | 2026-10-26 | cb1f627 | 15,947 B | A | view · diff |
| git:20261025.5c1b388 | 2026-10-25 | 5c1b388 | 15,781 B | A | view · diff |
| git:20261019.22de22a | 2026-10-19 | 22de22a | 14,168 B | A | view · diff |
| git:20261019.8fd294a | 2026-10-19 | 8fd294a | 14,120 B | A | view · diff |
| git:20261019.bfe1cee | 2026-10-19 | bfe1cee | 13,504 B | A | view · diff |
| git:20261018.464a31d | 2026-10-18 | 464a31d | 12,813 B | A | view · diff |
| git:20261018.40c63cc | 2026-10-18 | 40c63cc | 12,620 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16893 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
trustmybot/plugin · 6 stars · license MIT · pushed 2026-11-05 · branch dev
API
GET https://markdownregistry.com/api/v1/artifacts/art_c7jsqkc2qperb6da GET https://markdownregistry.com/api/v1/resolve?ref=trustmybot/plugin/tmb_planning GET https://markdownregistry.com/api/v1/blob/cfb1d577abe9ebf094e7fc2bcfe98ea9210aaae3eb46ec6cd742be459d83d5ff
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.