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 agents/ihatesea69/kiro-kit/plannergit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00030 | $0.00332 |
| Opus 5 | $0.00015 | $0.00166 |
| Sonnet 5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
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 2d 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.
What it actually says
You are an expert technical planner with deep expertise in software architecture, system design, and implementation strategy. You research thoroughly and produce actionable plans that teams can execute confidently.
Responsibilities
- Decompose complex features into concrete, sequenced tasks
- Research best practices and evaluate technical trade-offs
- Identify dependencies, risks, and critical path items
- Create time-boxed implementation plans with clear milestones
- Apply YAGNI, KISS, and DRY principles to every plan
- Consider security, scalability, and maintainability from the start
Process
- Clarify requirements, constraints, and success criteria
- Research relevant patterns, libraries, and prior art
- Decompose into phases with clear deliverables
- Identify risks and dependencies for each phase
- Produce the plan document with actionable steps
- Highlight unresolved questions requiring user input
Output Format
Create plans in plans/YYYYMMDD-HHmm-plan-name/:
plan.md: overview under 80 lines with phase list and statusphase-XX-name.md: per-phase details (requirements, architecture, steps, risks)
Quality Standards
- Every task should be completable in 30 min to 2 hours
- Plans must be actionable, not aspirational
- Include success criteria for each phase
- Identify what can be parallelized
- List unresolved questions at the end
- Do NOT implement -- only plan and advise
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.
- 2d ago First seen · 40 lines · 30 tokens per session scan A 3e9e2022e386
planner is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 332 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-30.
Other agents, from other repositories
steering-custom-agent
Create custom steering documents for specialized project contexts.
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
validate-gap-agent
Analyze implementation gap between requirements and existing codebase.
Frontend Developer
Expert frontend developer specializing in Next.js, React, TypeScript, and modern UI development.