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 skills/dentiny/kon/orchestrator-contextnpx skills add dentiny/kon --skill orchestrator-contextgit clone --depth 1 https://github.com/dentiny/konWrote 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/dentiny/kon/orchestrator-context)<a href="https://agentmods.dev/skills/dentiny/kon/orchestrator-context"><img src="https://agentmods.dev/badge/skills/dentiny/kon/orchestrator-context.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.00038 | $0.01167 |
| Opus 5 | $0.00019 | $0.00583 |
| Sonnet 5 | $0.00008 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
orchestrator-context 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Context Contract
Owner: orchestrator
Consumers: all /kon:* commands that spawn Task subagents (team, design, quick, debug, ask, research, review, begin routing, …)
Core principles (always): follow skills/core-principles — route by file pointer; don't restate or amplify subagent output (simplicity in orchestrator context).
Subagent Task returns enter the orchestrator's context window. Do not amplify bloat by quoting, restating, or forwarding that output in chat or in later spawn/resume prompts.
Full output lives in artifacts. Orchestrator holds pointers only.
Artifact map
| Agent | Full output artifact | When |
|---|---|---|
| Orchestrator | sessions/<SID>/understanding.md |
team, design, debug (orchestrator writes after pre-plan gate) |
| 🎸 Azusa | sessions/<SID>/explore.md |
/kon:team, /kon:design (subagentStop hook) |
| 🎸 Azusa | sessions/<SID>/debug.md |
/kon:debug (orchestrator writes once after Azusa) |
| 📚 Jun | .kon/research.md |
external research steps |
| 🍰 Mugi | PLAN_FILE (.kon/plan-<SID>.md or session plan) |
after plan step |
| 📝 Mio | sessions/<SID>/review.md |
team, quick, review, debug (subagentStop hook) |
| 📝 Mio | sessions/<SID>/pr-review.md |
/kon:review-pr |
| 📚 Jun | sessions/<SID>/issue-summary.md |
/kon:describe-issue |
| 📋 Nodoka | sessions/<SID>/summary.md |
/kon:summarize |
Resolve paths:
SID="<session-id>"
SESSION_DIR=$(python3 $KON_ROOT/scripts/kon_session.py session-dir --id "$SID")
REVIEW_FILE=$(python3 $KON_ROOT/scripts/kon_session.py artifact-path --id "$SID" --name review.md)
EXPLORE_FILE=$(python3 $KON_ROOT/scripts/kon_session.py artifact-path --id "$SID" --name explore.md)
Orchestrator rules
- User-facing messages — one line per agent step (verdict + artifact path). Never paste subagent output into assistant messages.
- Next spawn / resume prompts — file pointers + milestone/delta only. Never forward must-fix lists, explore findings, or review bodies through the orchestrator.
- Impl-loop handoffs — Yui and Mio resume and read
review.mddirectly. Seeskills/failure-handling. - Plan approval — present goal + step/milestone count +
## Decisions neededbullets; do not dump the full plan into chat (user opensPLAN_FILE). - After Task returns — call
complete-agentwith a one-sentence summary; do not copy the Task body into the summary field.
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 · 98 lines · 38 tokens per session scan A fc5c796a0d6e
orchestrator-context is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,167 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…