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/communicate)<a href="https://agentmods.dev/commands/sairam0424/mindforge/communicate"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/communicate.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.00034 | $0.00534 |
| Opus 5 | $0.00017 | $0.00267 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
mindforge:communicate 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/stakeholder-communication/SKILL.md </execution_context>
-
Communication Type Selection: For "update" → status report with progress metrics + blockers. For "risk" → impact assessment + mitigation options + decision request. For "proposal" → problem context + solution options + recommendation + trade-offs. For "decision" → decision record with rationale + alternatives considered + implementation plan.
-
Channel Optimization: Execs → brief written summary + optional sync for questions. Product → detailed narrative + visual roadmap. Engineering → technical RFC + architecture diagrams. Support → FAQ + runbook. External → polished deck + demo.
-
Message Structure: Open with TL;DR (1-2 sentences). Context section (why this matters now). Core content (structured by type). Action items (who/what/when). Appendix (supporting data/links).
-
Timing Strategy: Critical → synchronous escalation with written follow-up. Urgent → async with 24h response SLA. Normal → weekly update cycle. Low priority → monthly digest.
-
Feedback Loop Design: Specify response mechanism (reply/comment/meeting/survey). Set explicit decision deadline. Define escalation path if no response. Plan follow-up cadence (1 day/1 week/1 sprint).
-
Artifact Generation: Produce templated communication draft. Include pre-meeting agenda if sync. Generate post-communication summary template. Create decision log entry if applicable.
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 · 38 lines · 34 tokens per session scan A 0f75bdac27dd
mindforge:communicate is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 534 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-triage
Find open Linear issues for this repo and triage them toward agent-ready.
factory-sweep
Find Linear tickets that have gone obsolete (duplicate, already shipped, overtaken by events) and retire them with evidence.
factory-audit
Audit this repo against the project-conventions baseline; file the gaps to Linear.
factory-unblock
Re-examine held (ai:blocked) tickets for new evidence and release the ones that no longer need a human.
loops
Weekly review — surface everything in-flight and force a ship / block / kill decision on each.
p5-polish
Collects small clean-up TODOs accumulated during the sprint (from /p5-review, /p5-acceptance, /p5-bugfix, TODO/FIXME comments) that do not justify a full story but make the next sprint easier. Triages each item into polish-now, backlog, handover, or drop. Optionally executes polish-now items directly (TDD mini-cycle…