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/yonatangross/orchestkit/autonpx skills add yonatangross/orchestkit --skill autogit 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/skills/yonatangross/orchestkit/auto)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/auto"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/auto.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.00099 | $0.03385 |
| Opus 5 | $0.00049 | $0.01692 |
| Sonnet 5 | $0.00020 | $0.00677 |
| Haiku 4.5 | $0.00010 | $0.00338 |
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 today.
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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ork: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 106 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 /ork: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 | /ork:fix-issue |
| diagnose | why, why isn't, why does, why can't, investigate | /ork: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% | /ork:cover --target N |
| design | design, architect, how should we, explore, idea | /ork:brainstorm |
| build | build, implement, create, add feature, from ticket | /ork:implement |
| review | review, PR, MR, pull request, #N | /ork:review-pr |
| verify | verify, check, make sure, passes, green | /ork: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 ships with it
3 files 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.
- today First seen · 198 lines · 99 tokens per session scan A c1bf036ae386
auto is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 3,385 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
Agent Orchestrator
Coordinate multiple AI agents and skills for complex workflows.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.