update_reference

A command for updating a reference document by checking whether the sources it cites have changed. It keeps the document’s original purpose and structure.

In plain words
What is it for?
Use it to review a reference file, verify its cited sources, update affected content, refresh retrieval dates, and report breaking changes.
Why use it?
It helps prevent technical documentation from becoming outdated and highlights changes that could break existing code or instructions.

Command

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.

agentmods
npx agentmods add commands/jeffh/claude-plugins/update_reference
Clone the repo
git clone --depth 1 https://github.com/jeffh/claude-plugins
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,685 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00010 $0.03685
Opus 5 $0.00005 $0.01843
Sonnet 5 $0.00002 $0.00737
Haiku 4.5 $0.00001 $0.00368

Measured 2d ago against content hash 1d08985180e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

discuss/commands/update_reference.md · 496 lines

How it starts

The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Reference Document

You are tasked with updating an existing reference document by checking its cited sources for changes. You will identify what has changed, update the document accordingly, and provide a clear summary highlighting any breaking changes.

CRITICAL: YOUR PRIORITIES

  1. Breaking changes are the highest priority - Always identify and prominently call out breaking changes
  2. Preserve document intent - Update content without restructuring the document
  3. Source integrity - Maintain accurate source citations with current retrieval dates
  4. Conservative updates - Only update based on verifiable source changes

Initial Response

When this command is invoked:

If a file path was provided (e.g., /update-reference docs/zod-reference.md):

  • Immediately proceed to Step 1
  • Do not ask for confirmation

If no file path was provided, respond with:

I'll help you update a reference document by checking its sources for changes.

Please provide the path to the reference document you want to update.

Example: `/update-reference ./docs/my-library-reference.md`

Then wait for the user to provide the file path.

Steps to Follow

Step 1: Read and Parse the Document

  1. Read the reference document FULLY using the Read tool

    • IMPORTANT: Use the Read tool WITHOUT limit/offset parameters to read the entire file
    • This ensures you have complete context before analyzing
  2. Extract the Sources section:

    • Look for a "## Sources", "## References", or similar section
    • Parse all URLs listed (official docs, GitHub repos, blog posts, etc.)
    • Note retrieval dates if present
  3. If no Sources section found, respond with:

    I couldn't find a Sources section in this document. The /update-reference command requires a Sources section with URLs to check for updates.
    
    Would you like me to:
    1. Help you add a Sources section to this document
    2. Search for relevant sources based on the document content
    

    Then wait for the user's response.

Read the full file on GitHub · 496 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. 2d ago First seen · 496 lines · 10 tokens per session scan A 1d08985180e8

Subscribe to this mod's changes

update_reference is a command published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 17d ago), licensed Apache-2.0. It adds 10 tokens to every session and 3,685 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-08-30.