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/create-plan)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/create-plan"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/create-plan/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/create-plan"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/create-plan.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.00081 | $0.00751 |
| Opus 5.5 | $0.00032 | $0.00300 |
| Sonnet 5.5 | $0.00016 | $0.00150 |
| Haiku 4.5 | $0.00008 | $0.00075 |
Grade A, and why
create-plan 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 yesterday.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/create-plan/SKILL.md
Source: https://github.com/yonatangross/orchestkit
create-plan
Turn what is known about a task into one plan file that a person can review line by line. The plan lives in the task directory, and comments are written into the file, so the review history stays with the plan and survives a new session.
The layout (path, file name, front matter, comment block, the "done" signal) is fixed in
skills/create-plan/references/artifact-layout.md. Only skills/create-plan/scripts/artifact.mjs writes
the front matter.
Steps
-
Find the task directory. Ask for the task name if it was not given (kebab-case, one per branch, issue or lane). List what is already there:
node "skills/create-plan/scripts/artifact.mjs" status --task-dir .ork/tasks/<task> -
Read every artifact in it in full, in NN order: research, earlier plans, and their comment blocks. Open comments on an earlier artifact are requirements unless they were resolved.
-
Read the code the research points at. Every file the plan changes must be opened, so file paths and code in the plan are real.
-
Write the body to a scratch file, using skills/create-plan/references/plan-template.md. Each phase is testable on its own, names the files it changes, and ends with runnable automated checks.
-
Create the artifact through the script (never write the file directly):
node "skills/create-plan/scripts/artifact.mjs" create \ --task <task> --kind plan --slug <slug> --title "<title>" --author <your seat> --body /tmp/plan-body.md # prints .ork/tasks/<task>/NN-plan-<slug>.md -
Reply with the path and stop. Ask the reviewer to comment in the file (or run
/ork:review-artifact-commentsafter they do). Do not start implementing.
Rules
- When documents disagree, the newest wins: plan over research over the original ask.
- Out of scope is a section, not an afterthought: list what the plan will not do.
- Manual checks only where a person really has to look; do not pad phases with them.
- A second plan for the same task is a new artifact (new NN), not an edit of the old one. Revising
the same plan is
iterate-plan.
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.
- yesterday First seen · 63 lines · 81 tokens per session scan A 3e11c7b76e61
create-plan is a command published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 751 once invoked, about $0.0003 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-10-27.
Other commands, from other repositories
docs
Docs-only change for a ready-for-agent ticket. No application code.
lead
Tech lead: classify, quiz, ticket on the owning repo, dispatch. Do not implement.
handoff
Summarize the current work into a concise handoff for the next session (goal, done, state, next steps, risks).
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.