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 skills add qkitzero/kage-bunshin --skill plan-projectgit clone --depth 1 https://github.com/qkitzero/kage-bunshinWrote 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/qkitzero/kage-bunshin/plan-project)<a href="https://agentmods.dev/skills/qkitzero/kage-bunshin/plan-project"><img src="https://agentmods.dev/badge/skills/qkitzero/kage-bunshin/plan-project/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/skills/qkitzero/kage-bunshin/plan-project"><img src="https://agentmods.dev/badge/skills/qkitzero/kage-bunshin/plan-project.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.00045 | $0.00880 |
| Opus 5 | $0.00023 | $0.00440 |
| Sonnet 5 | $0.00009 | $0.00176 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
plan-project 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 10d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Project Skill
A workflow that creates an Agent Team of Researcher and Planner to create actionable project plans through iterative research and planning refinement.
Workflow
Step 1: Understand the Goal
Accurately understand the project goal/objective presented by the user. Clarify:
- Project goal (what to achieve)
- Scope (what's included, what's not)
- Known constraints (timeline, budget, personnel, tech stack, etc.)
- Definition of success (what does success look like)
Confirm with the user if ambiguous.
Step 2: Retrieve Past Notebook Context
If NOTEBOOK_PATH is set, search for past entries related to the project goal:
- Grep
$NOTEBOOK_PATH/plans/and$NOTEBOOK_PATH/research/for keywords from the goal - Also search for entries where the project name matches the
project:frontmatter - Read up to 3 matching entries (frontmatter + first 200 characters of body)
- Include the retrieved content as context when creating the team
Skip this step if zero matches or NOTEBOOK_PATH is not set.
Step 3: Create Agent Team
Create a team with the following teammates using their agent definitions from .claude/agents/:
Teammates:
researcher— gathers background knowledge and best practicesplanner— creates structured plans with tasks and dependencies
Team instructions:
Project goal: [User's goal]
Constraints: [User's constraints]
[Past Notebook context if found]
Collaboration protocol:
1. Researcher investigates: similar projects, best practices, pitfalls, required tech/resources, risks
2. Planner creates initial plan (phases, milestones, tasks, dependencies, risks)
3. Researcher reviews the plan for feasibility gaps — flags unrealistic estimates, missing risks, or overlooked dependencies based on research findings
4. Planner refines the plan based on Researcher's feedback
5. Continue iterating until both agree the plan is realistic and actionable (aim for 2-3 rounds)
Rules:
- Output language: Use the language specified by OUTPUT_LANGUAGE env var. If not set, match the user's language (default: English)
- If NOTEBOOK_PATH is set: Researcher saves to $NOTEBOOK_PATH/research/, Planner saves to $NOTEBOOK_PATH/plans/
- Each agent writes its own deliverables with structured frontmatter
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.
- 10d ago First seen · 120 lines · 45 tokens per session scan A 26ba20a7939d
plan-project is a skill published in the GitHub repository qkitzero/kage-bunshin (1 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 880 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
independent-review-loop
Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer…
writing-style
Structural pattern analysis for writing-mode review. Performs paragraph-level decomposition and pattern aggregation. Invoked by the team lead during editorial review.
code-mode
Code mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for code-mode teams.
writing-mode
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
triage-mode
Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.
gate-presentation
Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked by the team lead fresh on arrival at each gate and on pulse re-emissions, in the same turn as the render. The transport contract, three renders, partition rule…