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/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/release-sync)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/release-sync"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/release-sync/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/yonatangross/orchestkit/release-sync"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/release-sync.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.00062 | $0.01370 |
| Opus 5.5 | $0.00025 | $0.00548 |
| Sonnet 5.5 | $0.00012 | $0.00274 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
release-sync 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 26d 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/release-sync/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Release Content Sync
Sync the latest OrchestKit release to external knowledge systems.
CC ≥ 2.1.118 (M122): Sync triggers on the new
claude plugin tagannotated tag (in addition to plaingit tag). The tag's annotation embeds the plugin manifest version, which release-sync uses as the canonical source-of-truth for the version being synced. Seesrc/skills/chain-patterns/references/plugin-tag.md.
What This Does
- Reads the latest CHANGELOG entry, CLAUDE.md, and hook README
- Updates the OrchestKit NotebookLM KB notebook with fresh sources
- Ingests the release digest into HQ Knowledge Base (if available)
- Optionally generates a new podcast from the updated notebook
Prerequisites
- MCP servers:
notebooklm-mcpand/orhq-content - NotebookLM notebook ID stored in
.claude/release-sync-config.json
Step 1: Detect Version and Read Sources
# Read current version from CLAUDE.md
version = Grep(pattern="Current.*\\d+\\.\\d+\\.\\d+", path="CLAUDE.md")
# Read CHANGELOG — extract latest release section
changelog = Read("CHANGELOG.md", limit=80)
# Read hook architecture summary
hook_readme = Read("src/hooks/README.md", limit=100)
# Read CLAUDE.md for project overview
claude_md = Read("CLAUDE.md")
Step 2: Load Config
config = Read(".claude/release-sync-config.json")
# Expected format:
# {
# "notebooklm_notebook_id": "0a05e680-e33b-4d8c-94b2-5df26a1af329",
# "hq_kb_project": "orchestkit"
# }
If config doesn't exist, prompt user:
AskUserQuestion(questions=[{
"question": "NotebookLM notebook ID for OrchestKit KB?",
"header": "Configuration",
"options": [
{"label": "Use default", "description": "OrchestKit v7 — Complete KB (0a05e680...)"},
{"label": "I'll provide", "description": "Enter a custom notebook ID"}
]
}])
Step 2b: Choose Sync Targets
Ask for the four target values: notebooklm, hq_kb, slack, notes.
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.
- 26d ago Changed · -1 lines b0c7e8ec781c
- 1mo ago Changed d565bfdae10e
- 1mo ago First seen · 164 lines · 62 tokens per session scan A 68eee492cd2c
release-sync is a command published in the GitHub repository yonatangross/orchestkit (297 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,370 once invoked, about $0.0002 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
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
ship
Deliver completed work with validation and documentation.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.