update-component-reference

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

A command that adds a plugin component to a website’s documentation. It covers the component reference page, plugin index entry, and plugin README, using the named component as its input.

In plain words
What is it for?
It helps document skills, agents, or plugins in the website’s reference pages, update the plugin index, and create or refresh the relevant README.
Why use it?
It gives agents a defined documentation workflow for keeping the website and plugin materials aligned when a component is added or updated.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit It helps document skills, agents, or plugins in the website’s reference pages, update the plugin index, and create or refresh the relevant README.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/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.

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/commands/nikiforovall/claude-code-rules/update-component-reference/github.svg)](https://agentmods.dev/commands/nikiforovall/claude-code-rules/update-component-reference)
Your own site
<a href="https://agentmods.dev/commands/nikiforovall/claude-code-rules/update-component-reference"><img src="https://agentmods.dev/badge/commands/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/commands/nikiforovall/claude-code-rules/update-component-reference"><img src="https://agentmods.dev/badge/commands/nikiforovall/claude-code-rules/update-component-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 152 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.
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.00000 $0.00152
Opus 5.5 $0.00000 $0.00061
Sonnet 5.5 $0.00000 $0.00030
Haiku 4.5 $0.00000 $0.00015

Measured 1mo ago against content hash 5fb8ef963a9f, 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/commands/update-component-reference.md · 13 lines

What it actually says

description: Add plugin components to the website docs, including component reference pages, plugin index entries, and plugin READMEs argument-hint: Component or plugin to document (e.g., "skill glab", "agent code-reviewer", "plugin handbook-reflect") allowed-tools: ["Skill(update-component-reference)", "Read", "Write", "Edit", "Glob", "Grep", "Bash"]

Load the "update-component-reference" skill via Skill tool and follow its instructions.

When documenting a new plugin, also:

  • update the website plugin index in website/docs/plugins.md
  • add or refresh the plugin's concise README.md so the plugin structure matches repo conventions

Request: $ARGUMENTS

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 · 13 lines · 0 tokens per session scan A 5fb8ef963a9f

Subscribe to this mod's changes

update-component-reference is a command published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 152 tokens. 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.