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.
npx agentmods add skills/nikiforovall/claude-code-rules/update-component-referencenpx skills add NikiforovAll/claude-code-rules --skill update-component-referencegit clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWhat 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 | $0.00038 | $0.02004 |
| Opus 5 | $0.00019 | $0.01002 |
| Sonnet 5 | $0.00008 | $0.00401 |
| Haiku 4.5 | $0.00004 | $0.00200 |
Grade A, and why
update-component-reference 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.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Component Reference Skill
Add documentation for Claude Code components (commands, agents, skills, hooks, MCP servers) to the website's Component Reference section.
When to Use
Use this skill when the user requests to:
- Add a new component to the Component Reference documentation
- Document a newly created command, agent, skill, hook, or MCP server
- Update component documentation in the reference section
Prerequisites Checklist
Before documenting a component, ensure:
-
Component exists in the appropriate plugin directory:
- Commands:
plugins/handbook/commands/{name}.md - Agents:
plugins/handbook/agents/{name}.md - Skills:
plugins/handbook/skills/{name}/SKILL.md - Hooks:
plugins/{plugin-name}/hooks/hooks.jsonand hook scripts - MCP Servers:
plugins/{plugin-name}/.mcp.json
- Commands:
-
For skills only: Component is registered in plugin.json:
{ "skills": [ "./skills/skill-creator", "./skills/{new-skill-name}" ] } -
Verify plugin name: Check
.claude-plugin/plugin.jsonfor the badge (e.g., "handbook", "handbook-dotnet")
Implementation Process
Step 1: Determine Target Directory
Component documentation goes in: website/docs/component-reference/{type}/
- Commands →
website/docs/component-reference/commands/ - Agents →
website/docs/component-reference/agents/ - Skills →
website/docs/component-reference/skills/ - Hooks →
website/docs/component-reference/hooks/ - MCP Servers →
website/docs/component-reference/mcp-servers/
All category directories and _category_.json files already exist for these types.
Step 2: Determine sidebar_position
Read existing .mdx files in the target directory to find the highest sidebar_position and add 1.
Example:
grep -h "sidebar_position:" website/docs/component-reference/skills/*.mdx | sort -n
Step 3: Create Component Documentation File
Filename convention: Use kebab-case matching the component name
- Command
/commit→commit.mdx - Agent
@backend-architect→backend-architect.mdx - Skill
skill-creator→skill-creator.mdx - Hook
csharp-formatter→csharp-formatter.mdx - MCP Server
context7→context7.mdx
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 · 318 lines · 38 tokens per session scan A 5ad327d0cee8
update-component-reference is a skill published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,004 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.