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/kanevry/session-orchestrator/contract-version-bumpgit 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/contract-version-bump)<a href="https://agentmods.dev/commands/kanevry/session-orchestrator/contract-version-bump"><img src="https://agentmods.dev/badge/commands/kanevry/session-orchestrator/contract-version-bump.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 | $0.00035 | $0.00169 |
| Opus 5 | $0.00017 | $0.00084 |
| Sonnet 5 | $0.00007 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
contract-version-bump 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
/contract-version-bump
Use the Session Orchestrator command definition at commands/contract-version-bump.md.
Arguments: $ARGUMENTS
Read that command 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 command says to invoke a 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.
- 4d ago First seen · 15 lines · 35 tokens per session scan A 4b19cdf4d537
contract-version-bump is a command published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 169 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-08-30.
Other commands, from other repositories
cost-tracker
Track session costs, understand token spend, and get optimization tips.
plan
Generate specs/[###-feature]/plan.md from the active feature specification.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
commit
Quality-gated commit — runs lint/typecheck/test (if configured), reviews the staged diff, drafts a conventional-commits message, and commits.
audit-milestone
Audit milestone completion against original intent before archiving.
backlog
Manage backlog items — ideas not ready for active planning. Add, review, promote, or remove.