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 NikiforovAll/claude-code-rulesnpx agentmods add plugins/nikiforovall/claude-code-rules/handbook-code-reviewgit clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesGrade A, and why
handbook-code-review 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.
What it actually says
{
"name": "handbook-code-review",
"version": "1.0.1",
"description": "Code review plugin with a standalone reviewer agent and two skill strategies: disposable subagents for one-shot reviews and persistent team members for iterative reviews",
"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": [
"code-review",
"subagent",
"team",
"reuse",
"quality",
"efficiency"
]
}
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 · 21 lines scan A fe39fe34281b
handbook-code-review is a plugin published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 3d 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-08-30.
Other plugins, from other repositories
pm-ai-shipping
AI Shipping Kit — for PMs and founders accountable for AI-built code. Document a vibe-coded app, audit it for intended-vs-implemented security gaps and performance issues, and produce a reviewer-ready shipping packet.
pm-execution
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
smk
Plugin marketplace listing 13 plugins: cursor-delegate, spring-clean, portal-skills, readable, decode.
bash-specialist
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX via Charmbracelet gum. Skills: gum-beautify (TTY-safe interactive output). MCP: context7.
readable
Beautiful replies as styled cards (Persian/RTL always, English by default): the model sends content only, the template carries all styling. KPI grids, charts, trend sparklines, timelines, flows, callouts, badges, CTA buttons, content cards, side-by-side columns, quotes, section numbering and section breaks, a minimal…
cursor-delegate
Delegate self-contained coding/research tasks to the Cursor CLI (cursor-agent) from inside Claude Code, so they run on the Cursor subscription's quota instead of Claude's. One task via the cursor-delegate skill, or a whole fleet via cursor-orchestrate (Claude plans and reviews, Cursor executes in parallel). Workers…