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/release)<a href="https://agentmods.dev/commands/kanevry/session-orchestrator/release"><img src="https://agentmods.dev/badge/commands/kanevry/session-orchestrator/release/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/release"><img src="https://agentmods.dev/badge/commands/kanevry/session-orchestrator/release.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.00019 | $0.00157 |
| Opus 5.5 | $0.00008 | $0.00063 |
| Sonnet 5.5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
release 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.
This is a copy
86% identical to close — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/release
Use the Session Orchestrator skill definition at skills/release/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 983ee8a20b46
- 1mo ago Changed fdd7f86d17ce
- 1mo ago First seen · 15 lines · 19 tokens per session scan A 747b4396c618
release is a command published in the GitHub repository Kanevry/session-orchestrator (52 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 157 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to close, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
workweek-complete
Weekly release ceremony — validate, docs, release notes, merge.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
changelog
Generate changelog from session work with Problem/Solution format.
release
Increment version (SemVer), commit, and tag for release.
nyann:release
Cut a release: generate a CHANGELOG section from Conventional Commits, make a release commit, and create an annotated tag. Defaults to conventional-changelog strategy.