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-run-storygit 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-run-story)<a href="https://agentmods.dev/skills/kyzodb/plan/kyzo-plan-run-story"><img src="https://agentmods.dev/badge/skills/kyzodb/plan/kyzo-plan-run-story/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-run-story"><img src="https://agentmods.dev/badge/skills/kyzodb/plan/kyzo-plan-run-story.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.00056 | $0.00747 |
| Opus 5.5 | $0.00022 | $0.00299 |
| Sonnet 5.5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
kyzo-plan-run-story 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 ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 94 lines · 56 tokens per session scan A c0556c4f9931
kyzo-plan-run-story is a skill published in the GitHub repository kyzodb/plan (4 stars, last pushed 3mo ago), with no licence file. It adds 56 tokens to every session and 747 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 skills, from other repositories
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
testgen-flow
Workflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.
lov-atom-feature-dev
An end-to-end workflow for building a small, self-contained feature across its shared core, command-line tool, API, user interface, saved parameter presets, agent tool, and debugging panel. It uses one contract and shared test cases across the pieces.
sprint-conductor
Boot, run and resume the sprint QA conductor: one session that conducts a fleet of sprint-testing workers (one per ticket) on Orca and watches the whole sprint from one fixed point, the Sprint Board. Boots in one pass (sprint and board, the conductor-owned pre-flight, the Run, the sentinel, what the owner and the…
lov-atom-operations
A checklist and implementation workflow for making a completed feature ready to explain, test, find, authorize, sell, measure, and maintain. It decides which supporting work applies instead of adding every integration by default.
pdlc-feature
An automated workflow for taking a new software feature from a description or requirements document through requirements, design, testing, implementation, review, and release preparation. It keeps one feature ID across the documents and requires tests before implementation.