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 skills add kyzodb/plan --skill kyzo-plan-manage-boardgit 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/skills/kyzodb/plan/kyzo-plan-manage-board)<a href="https://agentmods.dev/skills/kyzodb/plan/kyzo-plan-manage-board"><img src="https://agentmods.dev/badge/skills/kyzodb/plan/kyzo-plan-manage-board/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/skills/kyzodb/plan/kyzo-plan-manage-board"><img src="https://agentmods.dev/badge/skills/kyzodb/plan/kyzo-plan-manage-board.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.00034 | $0.00213 |
| Opus 5 | $0.00017 | $0.00106 |
| Sonnet 5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
kyzo-plan-manage-board 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 11d 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.
- 11d ago First seen · 17 lines · 34 tokens per session scan A c82d2dd0dbb0
kyzo-plan-manage-board is a skill published in the GitHub repository kyzodb/plan (4 stars, last pushed 1mo ago), with no licence file. It adds 34 tokens to every session and 213 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-31.
Other skills, from other repositories
jira-bug-reporter
Create detailed bug reports from session evidence — auto-populate Jira tickets with session URLs, error messages, device info, and reproduction steps. Use when the user wants to file a bug from a Fullstory session.
pdlc-adopt
A tool for bringing an existing software project into a documented development process. It scans the project, identifies its services, applications, technologies, databases, and APIs, and can create baseline documents without changing code.
pdlc-status
A read-only progress overview for projects using PDLC, a documented process for moving a feature through stages such as design, testing, implementation, and review. It reads saved state files and groups work as ongoing, complete, or invalid.
pdlc-task
A task-tracking workflow for projects organized around a PRD, or product requirements document. It can split a feature into tasks and record each task as planned, active, completed, blocked, or reopened.
scan-projects
A skill that searches a configured directory for software projects and writes the results to projects-list.md. It recognises common project files, Git repositories, and Docker configuration files.
batch-init
An automation for finding software projects whose documentation is missing or out of date, then initializing those documents in batches. A batch is a group processed together, with no more than three projects handled at once.