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/agents/nikiforovall/claude-code-rules/plan)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/plan"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/plan/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/agents/nikiforovall/claude-code-rules/plan"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/plan.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.00004 | $0.00142 |
| Opus 5.5 | $0.00002 | $0.00057 |
| Sonnet 5.5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
plan 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
Planning mode instructions
You are in planning mode. Your task is to generate an implementation plan for a task.
The plan consists of the following sections:
- Overview: A brief description of the feature or refactoring task.
- Requirements: A list of requirements for the feature or refactoring task.
- Implementation Steps: A detailed list of steps to implement the feature or refactoring task.
Instructions
- Use a todos tool to create a todo list for the implementation steps.
- Don't make any code edits, just generate a plan.
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 · 17 lines · 4 tokens per session scan A 059e35c0a12b
plan is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 14d ago), licensed Apache-2.0. It adds 4 tokens to every session and 142 once invoked, about $0.0000 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-09-21.
Other agents, from other repositories
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
agent-creator
Generate the instruction bundle (AGENTS.md body, SOUL.md, HEARTBEAT.md, TOOLS.md) for a single Paperclip company agent. Use during company generation to write all agent files in parallel — one agent-creator instance per paperclip agent. Context: Company generation Phase 6a — writing agent files in parallel user…
skill-creator
Create properly structured SKILL.md files for Paperclip company agents. Use during company generation to write all custom skills in parallel. Context: Company generation Phase 6 — writing custom skills user: "Write 12 custom SKILL.md files for Figurio" assistant: "I'll use the skill-creator agent to generate properly…
demo-capture-operator
Captures ONE demo video section by driving the running app with the Playwright MCP video tools — rehearses it unrecorded, then records a single clip with human-feeling pointer motion, dwell timing, and per-character typing. Returns the clip path, its measured duration, and a deviation report. Invoke once per section…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…