update-component-reference

update-component-reference is a skill for Claude Code from NikiforovAll/claude-code-rules. It costs 38 tokens per session (2,004 once invoked), scanned A, original, Apache-2.0.

A documentation skill for adding Claude Code components—such as commands, agents, skills, hooks, and tool servers—to a website’s reference section.

In plain words
What is it for?
Checking that a component exists, confirming its plugin, and creating or updating its entry in the Component Reference documentation.
Why use it?
It provides a checklist and process so new component documentation is placed correctly and linked to an existing plugin.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions .claude-plugin; mentions Claude Code.

Good fit Checking that a component exists, confirming its plugin, and creating or updating its entry in the Component Reference documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nikiforovall/claude-code-rules/update-component-reference
Install

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.

Any agent
npx skills add NikiforovAll/claude-code-rules --skill update-component-reference
Clone the repo
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules

Made for: Claude Code.

Wrote 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.

agentmods badge for update-component-reference

README.md
[![agentmods](https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/update-component-reference/github.svg)](https://agentmods.dev/skills/nikiforovall/claude-code-rules/update-component-reference)
Your own site
<a href="https://agentmods.dev/skills/nikiforovall/claude-code-rules/update-component-reference"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/update-component-reference/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.

agentmods 80×15 button for update-component-reference

Your own site · 80×15
<a href="https://agentmods.dev/skills/nikiforovall/claude-code-rules/update-component-reference"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/update-component-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,004 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 146
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Rogue Agent · line 306
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.02004
Opus 5.5 $0.00015 $0.00802
Sonnet 5.5 $0.00008 $0.00401
Haiku 4.5 $0.00004 $0.00200

Measured 1mo ago against content hash 5ad327d0cee8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.claude/skills/update-component-reference/SKILL.md · 318 lines

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:

  1. 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.json and hook scripts
    • MCP Servers: plugins/{plugin-name}/.mcp.json
  2. For skills only: Component is registered in plugin.json:

    {
      "skills": [
        "./skills/skill-creator",
        "./skills/{new-skill-name}"
      ]
    }
    
  3. Verify plugin name: Check .claude-plugin/plugin.json for 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

Read the full file on GitHub · 318 lines

Changes

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.

  1. 1mo ago First seen · 318 lines · 38 tokens per session scan A 5ad327d0cee8

Subscribe to this mod's changes

update-component-reference is a skill published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 15d 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.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.

Related

Other skills, from other repositories

review-pr

Review a Pull Request in one of two postures: an expository "tour guide" that walks through changes in logical order, or an adversarial audit that assumes the change is wrong until proven safe and hunts for the failure mode. Triggers: "review PR #123", "adversarial review", "walk me through this PR", "PR tour guide"…

jontsai/claude-plugins · 139 tokens

researcher

Use when asked to create research documents, generate PDFs, make one-pagers, or create cheatsheets. Triggers: "research document", "generate PDF", "one-pager", "cheatsheet", "distinctive design". Provides HTML/Markdown/PDF with Terminal, Editorial, Corporate, Industrial, Fresh aesthetic presets.

jontsai/claude-plugins · 68 tokens

mem-rescue

Diagnose and fix memory pressure on a Mac (Linux best-effort) in one or two commands. Use whenever the user says their machine is slow, laggy, beachballing, out of memory, swapping, "swap is full", has low free memory, or that apps or browser tabs are crashing, failing to open, or being killed, even if they never say…

jontsai/claude-plugins · 143 tokens

svg-mastery

Expert knowledge for working with SVG (Scalable Vector Graphics) — optimization, embedding, animation, accessibility, responsive scaling, React integration, filters, and programmatic creation. Use when the user asks to "optimize SVG", "clean up SVG", "reduce SVG file size", "embed SVG in HTML", "inline SVG vs img…

lukaskellerstein/claude-my-marketplace · 276 tokens

demo-video

Orchestrates building a narrated demo video of a project — reads the codebase, writes a storyboard, prepares deterministic app state, drives the UI with Playwright to record clips (web and Electron, recorded by Playwright or by OBS), generates ElevenLabs voiceover, reconciles measured durations into a timeline, and…

lukaskellerstein/claude-my-marketplace · 144 tokens

visual-planning

ALWAYS use this skill FIRST, before producing or fetching ANY media asset — an image, video/GIF, chart, graph, diagram, infographic, SVG/icon, music, or speech/voiceover — and before any stock-photo search. It is the mandatory pre-generation gate. For a SINGLE asset it runs a short brief — clarify the ask → confirm…

lukaskellerstein/claude-my-marketplace · 271 tokens