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/commands/nikiforovall/claude-code-rules/slides)<a href="https://agentmods.dev/commands/nikiforovall/claude-code-rules/slides"><img src="https://agentmods.dev/badge/commands/nikiforovall/claude-code-rules/slides/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/commands/nikiforovall/claude-code-rules/slides"><img src="https://agentmods.dev/badge/commands/nikiforovall/claude-code-rules/slides.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.00010 | $0.00201 |
| Opus 5 | $0.00005 | $0.00101 |
| Sonnet 5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
slides 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 yesterday.
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
Load the visual-explainer skill, then generate a slide deck about the topic below. Any --flags in it belong to the skill's Arguments table, not to the topic.
Topic: $ARGUMENTS
Follow Slide Deck Mode in the skill — it owns the reading list, the narrative arc, and the composition rules.
Slide output is always opt-in. Only generate slides when this command is invoked or the user explicitly asks for a slide deck.
Aesthetic: pick one of the four slide presets in slide-patterns.md (Midnight Editorial, Warm Signal, Terminal Mono, Swiss Clean), or any --style value from the skill's table adapted for slides. Vary from previous decks and carry the choice through every slide.
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.
- yesterday First seen · 15 lines · 10 tokens per session scan A f6e43857cd6b
slides is a command published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 201 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
design
Create a design direction and styleguide for a project — produces aesthetic direction, fonts, colors, imagery, and media prompts.
architecture-diagram
Generate visual architecture diagrams using Mermaid including system architecture, data flow, and component relationships.
a11y-fix-focus
Fix keyboard and focus-management problems in a component and emit before/after diffs.
brand-new
Create a new visual brand profile via guided Q&A, optionally bootstrapping colors and fonts from an existing website, logo, or brand-guidelines PDF.
revisit
Go back to an earlier Design Thinking phase for iteration.
start
Initialize a new Design Thinking session from a pain point or problem statement.