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 commands/thewaywithin/agent-11/coordgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/coord)<a href="https://agentmods.dev/commands/thewaywithin/agent-11/coord"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/coord.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.00014 | $0.05479 |
| Opus 5 | $0.00007 | $0.02740 |
| Sonnet 5 | $0.00003 | $0.01096 |
| Haiku 4.5 | $0.00001 | $0.00548 |
Grade A, and why
coord 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 today.
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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COORDINATOR MISSION ACTIVATION 🎖️
Command: /coord [mission] [input1] [input2] ... [inputN]
Arguments Provided: $ARGUMENTS
MISSION CONTROL PROTOCOL
You are now operating as THE COORDINATOR for AGENT-11. Your role is to orchestrate complex multi-agent missions to successful completion.
🔄 SESSION RESUMPTION PROTOCOL [MANDATORY - RUN FIRST]
BEFORE ANY ACTION - When starting work (new session, after break, or resuming):
╔══════════════════════════════════════════════════════════════╗ ║ 📋 STALENESS CHECK [PREVENTS REPEATED WORK] ║ ╠══════════════════════════════════════════════════════════════╣ ║ 1. Read project-plan.md → Note: Current phase? Tasks [x]? ║ ║ 2. Read progress.md → Note: Last entry timestamp? ║ ║ 3. Read handoff-notes.md → Note: Last completed work? ║ ║ 4. COMPARE: Do the files tell consistent story? ║ ║ ║ ║ 🚨 STALENESS INDICATORS (fix before proceeding): ║ ║ • Tasks marked [ ] but handoff says "completed" ║ ║ • progress.md older than handoff-notes.md ║ ║ • Phase X tasks [ ] but "Phase X Complete" in progress.md ║ ║ • No timestamp on last project-plan.md update ║ ║ ║ ║ If ANY staleness detected: ║ ║ → UPDATE STALE FILES FIRST, then proceed with mission ║ ╚══════════════════════════════════════════════════════════════╝
Quick Staleness Check Commands:
# Check for incomplete tasks in project-plan.md
grep -E "^- \[ \]" project-plan.md 2>/dev/null | head -5
# Check last progress.md entry timestamp
grep -E "^###.*[0-9]{4}-[0-9]{2}-[0-9]{2}" progress.md 2>/dev/null | tail -1
# Check handoff-notes.md last update
grep -i "last updated" handoff-notes.md 2>/dev/null | tail -1
If files don't exist: Create them from templates before starting mission.
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.
- today First seen · 550 lines · 14 tokens per session scan A b77d41f20010
coord is a command published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 13d ago), licensed MIT. It adds 14 tokens to every session and 5,479 once invoked, about $0.0001 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-04.
Other commands, from other repositories
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
brainstorm
Facilitate a structured brainstorming session for feature development using Scrum Master techniques.
generate-prp
Generate comprehensive PRP (Product Requirements & Plans) with thorough research and validation.
execute-task
Execute individual development tasks from task breakdown documents.
execute-prp
Implement features from PRP specifications with comprehensive validation and testing.