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/kyzodb/planWrote 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/kyzodb/plan/kyzo-plan-development-task)<a href="https://agentmods.dev/agents/kyzodb/plan/kyzo-plan-development-task"><img src="https://agentmods.dev/badge/agents/kyzodb/plan/kyzo-plan-development-task/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/kyzodb/plan/kyzo-plan-development-task"><img src="https://agentmods.dev/badge/agents/kyzodb/plan/kyzo-plan-development-task.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.00055 | $0.00212 |
| Opus 5.5 | $0.00022 | $0.00085 |
| Sonnet 5.5 | $0.00011 | $0.00042 |
| Haiku 4.5 | $0.00006 | $0.00021 |
Grade A, and why
kyzo-plan-development-task 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 21 lines · 55 tokens per session scan A fa1be238cffc
kyzo-plan-development-task is an agent published in the GitHub repository kyzodb/plan (4 stars, last pushed 3mo ago), with no licence file. It adds 55 tokens to every session and 212 once invoked, about $0.0002 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
code-reviewer
Maintainability-focused code review - correctness, hidden coupling, testability, and regression risk. Use proactively after multi-file changes, before merging, or when asked to review a diff or PR. Reports findings ordered by severity. Read-only.
cto
Technical judgment lens - architecture, implementation strategy, tradeoffs, and maintainability direction. Use before significant implementation choices, when a design feels over- or under-engineered, or to sanity-check technical direction against the project stage. Advisory and read-only.
data-analytics
Measurement lens - success metrics, lightweight instrumentation, privacy boundaries, and review cadence. Use when defining what success looks like for a feature, adding analytics, or judging whether a claim about usage is actually measurable. Read-only.
delivery-lead
Execution lens - converts plans and council output into milestones, sequencing, dependencies, decisions, and next actions. Use at the end of planning work, when a project feels stuck, or when many open threads need turning into an ordered, owned plan. Read-only.
design-director
Experience and UI judgment lens - clarity, UX risks, visual coherence, accessibility, and user-facing polish. Use when reviewing screens, flows, copy, or any user-facing change, or when a feature works but does not feel right. Advisory and read-only.
growth-strategist
Launch and positioning lens - messaging, launch assets, distribution fit, credible claims, and feedback loops. Use when preparing a release announcement, README, landing page, or launch plan, or when checking that public claims match what the product actually does. Read-only.