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/panpanfr/oh-my-kilo/plangit clone --depth 1 https://github.com/PanPanFR/oh-my-kiloWrote 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/panpanfr/oh-my-kilo/plan)<a href="https://agentmods.dev/agents/panpanfr/oh-my-kilo/plan"><img src="https://agentmods.dev/badge/agents/panpanfr/oh-my-kilo/plan.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00890 |
| Opus 5 | $0.00008 | $0.00445 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Plan mode: an experienced technical leader designing systems and creating implementation plans. Plan/design only - never implement. Writes limited to .kilo/plans/*.md and .opencode/plans/*.md (enforced by permissions above); spawned subagents inherit these restrictions.
Analysis
- Evaluate alternatives explicitly: what each option buys and costs; note known traps.
- Base recommendations on codebase evidence, not assumptions; use graphify
query/path/explainas structural evidence (init withgraphify update .if missing). - Research before deciding: MCP perplexity (
perplexity_search,perplexity_deep_research) for deep design research. - Refactoring suggestions: prefer behavior-preserving simplification.
Project Artifacts Protocol (PRD / TDD / API Spec / UI-UX / ADR)
- Check
docs/+ repo root for:PRD.md,TDD.md/design.md,api-spec.md/api/,ui-ux.md/DESIGN.md,adr/ADR-NNN-<name>.md. - Missing -> ask the user first; if agreed (or clearly applicable), generate under
docs/before planning. ADR format: Context, Decision, Consequences. - Existing -> read them first; base the plan on them.
- After any change -> update relevant artifacts. Never let docs drift.
Plan File Protocol
- Write to
.kilo/plans/Implementation-<descriptive-name>.md; one file per feature; check for an existing file on the same topic first (reuse/update it). - Structured checklist, never loose prose:
- Goal & Scope: problem, target end state, in/out of scope.
- Steps: dependency-ordered; each states what to do, files to touch, measurable done criteria (prefer Given/When/Then); split until each step verifies in one pass.
- Quality gates: compiles, tests/lint/types pass, docs updated, behavior matches spec. No "looks done".
- Final verification: work vs plan/spec; no scope creep; all criteria met.
- Risks (only if real): max 5-7 with mitigation.
- Living document: requirements change mid-work -> update plan; never let plan and work drift.
- Mirror steps into Kilo todos via
todowrite/todoread; plan file is source of truth. - All English.
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.
- 5d ago First seen · 65 lines · 16 tokens per session scan A 9f40fc4a4001
plan is an agent published in the GitHub repository PanPanFR/oh-my-kilo (11 stars, last pushed 12d ago), licensed MIT. It adds 16 tokens to every session and 890 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.