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/Kanevry/session-orchestratorWrote 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/kanevry/session-orchestrator/plan)<a href="https://agentmods.dev/commands/kanevry/session-orchestrator/plan"><img src="https://agentmods.dev/badge/commands/kanevry/session-orchestrator/plan/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/commands/kanevry/session-orchestrator/plan"><img src="https://agentmods.dev/badge/commands/kanevry/session-orchestrator/plan.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.00074 | $0.00213 |
| Opus 5.5 | $0.00030 | $0.00085 |
| Sonnet 5.5 | $0.00015 | $0.00043 |
| Haiku 4.5 | $0.00007 | $0.00021 |
Grade A, and why
plan 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 1mo 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
/plan
Use the Session Orchestrator skill definition at skills/plan/SKILL.md.
Arguments: $ARGUMENTS
Read that skill file and follow it exactly. When it references $ARGUMENTS, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.
Cursor has no Skill tool. When the skill says to invoke another skill, Read skills/<skill-name>/SKILL.md and follow it. Supporting files (soul.md, phase docs) live in that same skills/<skill-name>/ directory.
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.
- 1mo ago Changed · +1 lines · +61 tokens per session 70fb4c54465b
- 1mo ago Changed 3879a110d01b
- 1mo ago First seen · 15 lines · 13 tokens per session scan A 439a481c2e5c
plan is a command published in the GitHub repository Kanevry/session-orchestrator (53 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 213 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-08-30.
Other commands, from other repositories
heartbeat
Run a WoterClip heartbeat cycle (pick up issues, do work, report).
woterclip-status
Show WoterClip status (queue, blocked issues, last heartbeat).
docs
Docs-only change for a ready-for-agent ticket. No application code.
lead
Tech lead: classify, quiz, ticket on the owning repo, dispatch. Do not implement.
decree
Issue a decree. Seats the organization on first use, then dispatches the teams.
bob-work
Drain the board as a worker — claim pending tasks Claude can do, execute them, submit results.