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.
git clone --depth 1 https://github.com/sairam0424/MindForgeWrote 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/commands/sairam0424/mindforge/dmux)<a href="https://agentmods.dev/commands/sairam0424/mindforge/dmux"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/dmux.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.1 | $0.00040 | $0.00347 |
| Opus 5 | $0.00020 | $0.00173 |
| Sonnet 5 | $0.00008 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
dmux 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 4d 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
<execution_context> @.mindforge/skills/dmux-workflows/SKILL.md @.mindforge/skills/rfc-pipeline/SKILL.md </execution_context>
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.
- 4d ago First seen · 33 lines · 40 tokens per session scan A ec0d572cf1be
dmux is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 347 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
factory-merge
Review open PRs thoroughly, fix what's fixable, merge what's good.
close
End session with verification, commits, and documentation.
commit-all
Stage and commit all current changes with a single message. Auto Git Push will pick up and push to origin within 30s.
factory-work
Dispatch subagents to work agent-ready Linear tickets, land the PRs, report.
anchor
Checks phase documents against the code they describe, not against other documents. Where /cross-check compares Markdown to Markdown, /anchor compares a document's declared anchorcommit to the repository's actual history — the two-stage check design of docs/adr/ADR-0009-anchored-state-verification.md (both addenda).
p4-setup
Sets up the repository, CI/CD pipeline and local development environment. The result is a working development infrastructure in which the team can immediately start with /p5-implement.