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 receptron/mulmoterminal --skill tranchegit clone --depth 1 https://github.com/receptron/mulmoterminalWrote 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/receptron/mulmoterminal/tranche)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/tranche"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/tranche/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/receptron/mulmoterminal/tranche"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/tranche.svg" alt="Reviewed on agentmods" width="80" 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.00069 | $0.02741 |
| Opus 5.5 | $0.00028 | $0.01096 |
| Sonnet 5.5 | $0.00014 | $0.00548 |
| Haiku 4.5 | $0.00007 | $0.00274 |
Grade A, and why
blueprint-refactor-tranche 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 14d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One target, one change
This step repeats. Each round does one target from .blueprint/targets.json — the first whose status
is todo — and nothing else. The whole claim of the change is "this behaves the same", and that is
not provable by reading. What follows is how it is proved instead.
Read .blueprint/spec.md (the plan the person approved), .blueprint/gates.json (the gates) and
.blueprint/answers.json (merge: whether to merge on green CI).
0. The approved plan wins
The person may have changed the plan by talking to it at the review gate, which rewrites spec.md but not
targets.json. If the two disagree — a target added, dropped, reordered or reworded — bring
targets.json in line with spec.md first. Keep finished targets as they are.
A ci target
Close the gaps in .blueprint/ci.json with the smallest change: prefer adding a step to the workflow that
already installs dependencies over a new workflow, and use the install command from gates.json. Every
workflow gets a top-level permissions: block (default contents: read; a job gets more only if it needs
it) and actions/checkout gets persist-credentials: false. Then continue from step 8 — the pull request's
own checks are the proof that the new CI runs and passes.
1. Start clean, and check nobody else is in the file
- On the default branch,
git pull --ff-only. Branch:blueprint/<target id>. gh pr list --state openandgit log origin/<default> --oneline -20 -- <files>. A pull request merged an hour ago is in neither your tree nor the open list. If someone else is changing these lines, mark the targetskippedwith that as the note, and stop the round.- Confirm the target is still reachable: grep for its caller or renderer, not its import.
2. Find the guards before touching anything
grep -rln "<file basename>" test/ tests/ src/ --include='*.test.*' --include='*.spec.*'
grep -rn "'<identifier>'\|\"<identifier>\"" test/ tests/ src/
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.
- 14d ago Changed · +11 lines 4584d3a8d13a
- 19d ago First seen · 173 lines · 69 tokens per session scan A f992e28da2e9
blueprint-refactor-tranche is a skill published in the GitHub repository receptron/mulmoterminal (239 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 2,741 once invoked, about $0.0003 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-09-28.
Other skills, from other repositories
using-orc
If you were dispatched as a subagent to execute a specific task, skip this skill.
clean-merge-lands-line-guard-on-a-value-neither-branch-predicted
Two branches each contain a guard, test or document that pins a line NUMBER in a third file, each side correctly re-aims that number for its own tree, and git merges both edits with NO conflict — leaving a merged tree whose real line can be neither number. Use when: (1) two parallel PRs both insert or delete lines in…
isolate-subagent-verification-from-live-worktree
A verification / gate-running subagent you dispatched into YOUR OWN worktree silently measures the branch PLUS your uncommitted edits, and reports the mixture as the branch's result. Nothing is clobbered and nothing errors — the suite really ran, the counts are real, they are just counts of a tree nobody will ever…
prove-test-failures-pre-existing-via-clean-worktree
After making a change you run the test suite and it shows failures — especially in files/areas your diff never touched, or a count that "feels unrelated." Before you either panic-debug them OR wave them off as "probably pre-existing," PROVE it: run the exact failing tests against a clean checkout of origin/main (a…
worktree-historical-test-replay-missing-dirs
Fix pytest exit 4 ("file or directory not found") when running a test command in a git worktree checked out at an OLD commit. Use when: (1) you're doing historical replay (incident replay, mutation testing, git bisect with tests) and the suite errors out in 1-2 seconds with no test execution, (2) the test command…
tdd
Enforces red-green-refactor TDD cycle with atomic commits per phase. Used when implementing features, fixing bugs, or when tests should drive the design.