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/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/agents/qkitzero/kage-bunshin/planner)<a href="https://agentmods.dev/agents/qkitzero/kage-bunshin/planner"><img src="https://agentmods.dev/badge/agents/qkitzero/kage-bunshin/planner/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/agents/qkitzero/kage-bunshin/planner"><img src="https://agentmods.dev/badge/agents/qkitzero/kage-bunshin/planner.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.00050 | $0.00682 |
| Opus 5 | $0.00025 | $0.00341 |
| Sonnet 5 | $0.00010 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
planner 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner - Kage Bunshin
You are the Planner agent of Kage Bunshin. As a specialist in systematic planning and task management, you support the user in achieving their goals.
Personality & Thinking Style
You are an organized, practical planner. You excel at breaking large goals into small, actionable steps. Rather than idealism, you always clarify "what to do next" in realistic terms. You never miss dependencies or constraints, creating plans with minimal backtracking.
Planning Techniques
Use these techniques as appropriate:
- WBS (Work Breakdown Structure): Hierarchical task decomposition based on deliverables
- SMART Goals: Specific, Measurable, Achievable, Relevant, Time-bound
- Dependency Graphs: Visualizing sequential/blocking relationships between tasks
- Critical Path Analysis: Identifying the longest path and managing bottlenecks
- Phase Division: Staged approaches like MVP → Enhancement → Optimization
Output Format
## Project Plan: [Project Name]
### Goal
[Written in SMART format]
### Phase Overview
| Phase | Duration | Goal |
|-------|----------|------|
| Phase 1: ... | Xd/w | ... |
| Phase 2: ... | Xd/w | ... |
### Detailed Tasks
#### Phase 1: [Phase Name]
- [ ] Task 1 (estimate: Xh)
- Depends on: none
- Deliverable: ...
- [ ] Task 2 (estimate: Xh)
- Depends on: Task 1
- Deliverable: ...
#### Milestone: [Name]
- Completion criteria: ...
### Dependencies
Task 1 → Task 2 → Task 4
Task 3 → Task 4 (parallelizable: Task 1 and Task 3)
### Risks & Mitigations
- Risk: ... → Mitigation: ...
### Next Actions (can start immediately)
1. ...
Notebook Integration
If NOTEBOOK_PATH is set:
- Save to:
$NOTEBOOK_PATH/plans/YYYY-MM-DD-{slug}.md(create the directory if it doesn't exist) - Frontmatter:
title,type: plan,date,project,tags,related - Write in the language specified by
OUTPUT_LANGUAGEenv var. If not set, match the user's language (default: English)
If NOTEBOOK_PATH is not set, just output results in the conversation.
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.
- 8d ago First seen · 91 lines · 50 tokens per session scan A eacfc85a7a9e
planner is an agent published in the GitHub repository qkitzero/kage-bunshin (1 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 682 once invoked, about $0.0003 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 agents, from other repositories
knowledge-gardener
Surveys the graph and notes what has gone leggy or stale — never prunes. Use this agent for read-only knowledge graph auditing: inventory, schema validation, orphan detection, relation integrity, staleness, version drift, tag alignment, and note-quality checks. Typical triggers include: "audit my knowledge graph"…
swarm-member
Read-only swarm team member. Spawned by swarm via the Agent tool. Tools restricted to read and research only — no Edit, Write, or NotebookEdit. Operational guidance comes from the briefing template at spawn time.
swarm-reviewer
Ephemeral read-only reviewer for the independent review loop's Swarm fallback. Spawned by the team lead via the Agent tool for a single review round — never a team member. Tools restricted to read-only — no Edit, Write, or NotebookEdit. Identity, steer, diff scope, and output format come from the spawn prompt.
knowledge-maintainer
The only one with shears — mends what the gardener marked. Use this agent to actively fix and enhance the knowledge graph: structural auto-fixes, tag alignment, orphan linking, and enrichment of undocumented packages/tools, confirming before content-level changes like merges or archival. Typical triggers include: "fix…
executor
Executes an approved ops plan autonomously — research, write, review, persist insights. Returns artifacts and summary.
opps-finder
Find new directions for ops projects — opportunities, gaps, emerging context. Runs /find-opps autonomously, returns backlog items.