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/NikiforovAll/claude-code-rulesWrote 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/plugins/nikiforovall/claude-code-rules/handbook-structured-plan-mode)<a href="https://agentmods.dev/plugins/nikiforovall/claude-code-rules/handbook-structured-plan-mode"><img src="https://agentmods.dev/badge/plugins/nikiforovall/claude-code-rules/handbook-structured-plan-mode/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/plugins/nikiforovall/claude-code-rules/handbook-structured-plan-mode"><img src="https://agentmods.dev/badge/plugins/nikiforovall/claude-code-rules/handbook-structured-plan-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
handbook-structured-plan-mode 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 25d 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.
What it actually says
{
"name": "handbook-structured-plan-mode",
"version": "1.19.6",
"description": "Structured planning methodology for complex feature implementations through systematic task decomposition",
"author": {
"name": "nikiforovall",
"url": "https://github.com/nikiforovall"
},
"homepage": "https://nikiforovall.blog/claude-code-rules/",
"repository": "https://github.com/nikiforovall/claude-code-rules",
"license": "MIT",
"keywords": [
"planning",
"task-management",
"project-management",
"workflow",
"feature-development",
"productivity"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 64 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 25d ago First seen · 21 lines scan A 0a674eb4eebc
handbook-structured-plan-mode is a plugin published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 14d ago), licensed Apache-2.0. 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-09-21.
Other plugins, from other repositories
ccx
Scratch-notebook context management for any project: per-thread STATE.md handoff docs with one-command create-or-resume (/ccx:start-thread), a compiled parallel-session-safe INDEX dashboard that recompiles itself on every STATE write (/ccx:save-state · /ccx:tidy-scratch), a Stop-hook freshness guard so working state…
paperclip-plugin
Autonomous AI company advisor for the Paperclip platform — create, design, and manage AI-powered companies with proper agent hierarchies, runtime configurations, and infrastructure following the Agent Companies spec (agentcompanies/v1).
pm-execution
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
pm-product-strategy
Product strategy skills for PMs: vision, strategy canvas, value propositions, lean canvas, business model canvas, SWOT, PESTLE, Ansoff Matrix, Porter's Five Forces, and monetization.
team-motivation
Team motivation and management skills including Daniel Pink's Autonomy, Mastery, Purpose (AMP) principles and Andy Grove's High Output Management (leverage, one-on-ones, OKRs, task-relevant maturity).
odin-core
Core ODIN gates every session runs: intent, scope, verification, and hand-off checks.