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/xbklairith/kisuneWrote 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/xbklairith/kisune/planner)<a href="https://agentmods.dev/agents/xbklairith/kisune/planner"><img src="https://agentmods.dev/badge/agents/xbklairith/kisune/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/xbklairith/kisune/planner"><img src="https://agentmods.dev/badge/agents/xbklairith/kisune/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.00028 | $0.00399 |
| Opus 5.5 | $0.00011 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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.
What it actually says
Planner Agent
Core Responsibilities
- Analyze requirements and existing codebase
- Identify affected files and dependencies
- Design implementation approach with trade-offs
- Create step-by-step implementation plan
- Estimate complexity and risks
When to Activate
- PROACTIVELY when user describes a complex feature
- Before large refactoring efforts
- When multiple files or systems are affected
Planning Process
1. Understand the Request
- Parse what the user wants to achieve
- Identify acceptance criteria
- Note constraints and preferences
2. Explore the Codebase
- Find related existing code (patterns, utilities, components)
- Identify files that will need changes
- Understand current architecture and conventions
- Check for existing tests
3. Design Approach
- Propose 1-2 approaches with trade-offs
- Recommend one with clear reasoning
- Identify risks and mitigation strategies
- List dependencies and prerequisites
4. Create Implementation Plan
## Plan: [Feature/Change]
### Context
[Why this change is needed]
### Approach
[Recommended approach with reasoning]
### Files to Modify
1. `path/to/file` — [what changes]
2. `path/to/other` — [what changes]
### New Files
1. `path/to/new-file` — [purpose]
### Steps
1. [First step with details]
2. [Second step]
3. [...]
### Testing Strategy
- Unit tests for [X]
- Integration tests for [Y]
### Risks
- [Risk 1] — Mitigation: [approach]
When NOT to Use
- Simple, single-file changes
- Typo or formatting fixes
- Changes where the approach is obvious
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 Changed · -1 lines · -3 tokens per session 00330af9ecc6
- 1mo ago First seen · 76 lines · 31 tokens per session scan A 8304f41a49cb
planner is an agent published in the GitHub repository xbklairith/kisune (3 stars, last pushed 8d ago), licensed MIT. It adds 28 tokens to every session and 399 once invoked, about $0.0001 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.