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/yonatangross/orchestkitnpx agentmods add commands/yonatangross/orchestkit/implementWrote 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/implement)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/implement"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/implement/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/implement"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/implement.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.00091 | $0.06558 |
| Opus 5.5 | $0.00036 | $0.02623 |
| Sonnet 5.5 | $0.00018 | $0.01312 |
| Haiku 4.5 | $0.00009 | $0.00656 |
Grade A, and why
implement 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/implement/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Implement Feature
Host-neutral workflow. Invoke by skill name (implement). Claude Code slash routing, YAML hook loaders, and .claude/chain live in skills/implement/references/claude-code.md.
Parallel subagent execution for feature implementation with scope control and reflection.
Quick Start
implement user authentication
implement --model=opus real-time notifications
implement dashboard analytics
Argument Resolution
Check the target first, before any other step. This skill forks and cannot see the conversation. Load Read("../../shared/rules/target-resolution.md"): if the target, flags stripped, is a bare pronoun or deictic (this, them, that one) or empty, return exactly TARGET_UNRESOLVED: <word> and stop. The caller resolves it and re-invokes.
FEATURE_DESC = "$ARGUMENTS" # Full argument string, e.g., "user authentication"
# $ARGUMENTS[0] is the first token, $ARGUMENTS[1] second, etc. (CC 2.1.59)
# Model override detection (CC 2.1.72)
MODEL_OVERRIDE = None
for token in "$ARGUMENTS".split():
if token.startswith("--model="):
MODEL_OVERRIDE = token.split("=", 1)[1] # "opus", "sonnet", "haiku", "fable"
FEATURE_DESC = FEATURE_DESC.replace(token, "").strip()
Pass MODEL_OVERRIDE to all Agent() calls via model=MODEL_OVERRIDE when set. Accepts symbolic names (opus, sonnet, haiku, fable on harnesses whose Agent tool lists it; note fable is premium API spend after 2026-07-12) or full IDs (claude-opus-5-5) per CC 2.1.74.
Step -1: MCP Probe + Resume Check
Run BEFORE any other step. Detect available MCP servers and check for resumable state.
# Probe MCPs (parallel — all in ONE message):
# memory is alwaysLoad in .mcp.json (CC 2.1.121+, #1541) — probe below kept as fallback for older CC:
ToolSearch(query="select:mcp__memory__search_nodes")
ToolSearch(query="select:mcp__context7__resolve-library-id")
Write(".claude/chain/capabilities.json", JSON.stringify({
"memory": <true if found>,
"context7": <true if found>,
"timestamp": now()
}))
# Resume check:
Read(".claude/chain/state.json")
# If exists and skill == "implement":
# Read last handoff (e.g., 04-architecture.json)
# Skip to current_phase
# "Resuming from Phase {N} — architecture decided in previous session"
# If not: write initial state
Write(".claude/chain/state.json", JSON.stringify({
"skill": "implement", "feature": FEATURE_DESC,
"current_phase": 1, "completed_phases": [],
"capabilities": capabilities,
"budget_remaining_pct": 100 // advisory; see Budget Awareness below
}))
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 · +12 lines 9347e1fa17c6
- 15d ago Changed b9c4a531cb1b
- 17d ago Changed 5df5c6f1f5ff
- 21d ago Changed b9ce6a783497
- 23d ago Changed · +2 lines e538bb674b22
- 24d ago Changed f737a530498a
- 1mo ago Changed 6db9eee266b3
- 1mo ago Changed 16d19e0a0ecc
- 1mo ago First seen · 478 lines · 91 tokens per session scan A 96659f2ea282
implement is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 6,558 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.