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/auto)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/auto"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/auto/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/auto"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/auto.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.00099 | $0.03472 |
| Opus 5.5 | $0.00040 | $0.01389 |
| Sonnet 5.5 | $0.00020 | $0.00694 |
| Haiku 4.5 | $0.00010 | $0.00347 |
Grade A, and why
auto 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 5d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/auto/SKILL.md
Source: https://github.com/yonatangross/orchestkit
auto — Intent Router
The front door to OrchestKit. You describe a goal in plain English; the router classifies it and hands off to the right specialist. One entry point, many execution paths.
Why this exists: OrchestKit has 110 skills, but usage telemetry shows users fire only the handful they can name by memory (10 distinct skills across thousands of sessions). The dominant cause of "dead" skills is no front door — not low quality. This router turns "you must know the exact
/ork:<name>" into "describe what you want."
Core principle: routing is a deterministic workflow, not an autonomous agent (Anthropic, Building Effective Agents). Classify → confirm → hand off. The router never does the work itself — it picks who does.
When to use
By default, for any goal-shaped request. An unambiguous goal is a 1-step route: auto classifies, confirms in one line, and hands off — no extra hops, so there is no "too obvious for auto".
Use auto for… |
Skip only when… |
|---|---|
| Any goal description ("fix X", "get Y to Z") | Already executing inside another skill (no recursion) |
| The right skill isn't obvious | Chaining a known multi-skill workflow you're mid-way through |
| You think you know the skill — auto confirms & short-circuits |
Design note (2026-07-12): this table previously said "Go direct when you already know the skill / the request maps unambiguously to one". That inverted instruction made the front door structurally unreachable — a competent model always believes it knows the target, so the router recorded near-zero invocations across thousands of sessions (the exact dead-skill problem the "Why this exists" note above describes). Routers must be framed as the default path, not an escape hatch for confusion.
Intent categories → OrchestKit skill
| intent | signal words | routes to |
|---|---|---|
| fix | fix, debug, broken, failing, error, crash, regression | fix-issue |
| diagnose | why, why isn't, why does, why can't, investigate | fix-issue (investigation-first) |
| optimize | faster, reduce, latency, bundle, minimize, below N ms | a /goal optimization loop (see Gaps) |
| cover | coverage, untested, get to N% | cover --target N |
| e2e | e2e, in the browser, browser test, playwright | expect (run on the diff); cover when no e2e tests exist yet |
| design | design, architect, how should we, explore, idea | /ork:brainstorm |
| build | build, implement, create, add feature, from ticket | implement |
| review | review, PR, MR, pull request, #N | review-pr |
| verify | verify, check, make sure, passes, green | verify |
| improve-skill | improve the skill, optimize the prompt, SKILL.md | the holdout-promotion gate (see Gaps) |
| (fallback) | no confident category | clarify with ONE question |
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.
- 5d ago Changed · +1 lines 1fb2305bb814
- 9d ago Changed · +1 lines a3203769247d
- 15d ago Changed 500a01cc121c
- 17d ago Changed c674cca922fd
- 21d ago Changed 2bfe794a632d
- 22d ago Changed 5a749a3b0102
- 23d ago Changed a96d06d9ca96
- 28d ago Changed · +2 lines ed4f2911e8f8
- 1mo ago Changed 255f9485db56
- 1mo ago First seen · 185 lines · 99 tokens per session scan A dd8f5ac1f582
auto is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 3,472 once invoked, about $0.0004 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
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
pn-distill
Remove content, sections, and features that don't earn their place — information architecture reduction. Use when there's too much stuff on the page. For visual decoration reduction, use pn-quieter.
distil-shadow
Decision-equivalence report — did compression preserve your agent's next action?
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.