Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Kanevry/session-orchestratornpx agentmods add skills/kanevry/session-orchestrator/releaseWrote 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/skills/kanevry/session-orchestrator/release)<a href="https://agentmods.dev/skills/kanevry/session-orchestrator/release"><img src="https://agentmods.dev/badge/skills/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/skills/kanevry/session-orchestrator/release"><img src="https://agentmods.dev/badge/skills/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.00021 | $0.00325 |
| Opus 5.5 | $0.00008 | $0.00130 |
| Sonnet 5.5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
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
92% identical to close — 9 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
Portable mirror — generated, do not edit. The canonical workflow lives at
skills/release/SKILL.md; read that file for the full instructions. This mirror carries only agentskills.io-spec-legal frontmatter so harnesses that discover skills under.agents/skills/can find and route to the skill.Regenerate with
node scripts/generate-agents-skills.mjs.
Read the linked document in full and follow its complete workflow, including prechecks and stop conditions. Resolve its link relative to this SKILL.md, not the project working directory. The plugin root is three directories above this file. Resolve package paths such as skills/ and scripts/ from that root and relative links in the canonical document from its own directory. Keep the user’s project as the target of project operations.
$ARGUMENTS means the trailing user input after the selected command skill, or an empty string when absent. Preserve flags, quoted text, and Unicode as data. Do not perform global substitution in the command document, shell expansion on the argument string, or execution of that string as shell code. Pass command arguments through structured tool parameters or safely quoted individual arguments.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +4 lines 6070899a83f1
- 1mo ago Changed · +2 lines b4ed55cb3372
- 1mo ago Changed · -6 lines 7bc68ef022e3
- 1mo ago First seen · 23 lines · 21 tokens per session scan A c3a2682d2c13
release is a skill published in the GitHub repository Kanevry/session-orchestrator (53 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 325 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to close, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
git-pr-strategy
Apply safe branching, commits, conflict resolution, review ownership, merge, rollback, and release-tag rules.
pace-release
A release-management workflow for coordinating software versions from preparation through deployment and closure. A release is a planned delivery of changes to users or an environment.
merging-to-main
Keyword-gated by name. Merge a ready branch to main via PR.
finishing-a-development-branch
Presents merge, PR, or cleanup options once tests pass.
matilha-gather
Use when completed subprojects are ready to merge — validates SP-DONE.md strict gates, merges --no-ff in mergeorder, runs per-SP regression, updates wave-NN-status.md.