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.
/plugin marketplace add kyzodb/plannpx agentmods add plugins/kyzodb/plan/marketplacegit clone --depth 1 https://github.com/kyzodb/planGrade A, and why
kyzo 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 2d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
1 file beside marketplace.json 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.
- 2d ago First seen · 15 lines scan A b3f694f358d8
kyzo is a plugin published in the GitHub repository kyzodb/plan (4 stars, last pushed 1mo ago), with no licence file. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ai-sdlc-harness
AI-driven SDLC workflow harness — multi-agent dev with plan → code → review → test → PR.
ai-agents-skills
Skills + hooks for Claude Code: teamlead (main thread as team-lead: delegate code work to subagents, surface only decisions), roadmap (plan & autonomously build a whole app phase-by-phase), kanban (manage a .claude/kanban board), schedule-tasks (auto-pilot todo cards via at/tmux), git-flow (shared git core: commits.
bergant-workflow
Engineering workflow plugin: spec-to-docs (project-init) and feature lifecycle orchestration (lifecycle) with compact/gate-enforcement hooks.
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
bugscribe
A single skill that files one already-identified bug as a new GitHub issue: verifies the defect against the source code, checks the backlog for duplicates, posts a short report pointing to a file and line, and pings the repository owner exactly once — it reports a known finding rather than searching for one.