repo

repo is a skill for Claude Code from L3DigitalNet/Claude-Code-Plugins. It costs 51 tokens per session (1,115 once invoked), scanned A, original, MIT.

A repository documentation updater that turns a session-change summary into changes for README.md, docs, CLAUDE.md, and related project guidance.

In plain words
What is it for?
Use it after development sessions when project documentation needs to be updated from the recorded changes.
Why use it?
It helps the repository’s instructions reflect known changes without inventing or fixing unrelated differences.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the up-docs plugin — 5 skills, 4 agents shipped together

Good fit Use it after development sessions when project documentation needs to be updated from the recorded changes.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add L3DigitalNet/Claude-Code-Plugins
Claude Code
/plugin install up-docs

Made for: Claude Code.

Or install up-docs, the plugin that ships this one along with the rest of its 5 skills, 4 agents.

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 repo

README.md
[![agentmods](https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/repo.svg)](https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/repo)
Your own site
<a href="https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/repo"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/repo.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,115 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.00051 $0.01115
Opus 5 $0.00026 $0.00558
Sonnet 5 $0.00010 $0.00223
Haiku 4.5 $0.00005 $0.00112

Measured 4d ago against content hash f0e09ee0f8d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

repo 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 4d 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.

plugins/up-docs/skills/repo/SKILL.md · 72 lines

How it starts

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

/up-docs:repo

Update the active repo's docs via the up-docs-propagate-repo sub-agent (Sonnet).

Workflow

0. Pre-flight: Dirty-tree guard

Before doing anything else, check for uncommitted changes (staged, unstaged, or untracked — --porcelain reports all three, and the STOP applies to all three):

git status --porcelain

If the output is non-empty, STOP immediately:

  • Emit the list of dirty files to the user.
  • Refuse with: "Uncommitted changes detected — stash or commit them before running /up-docs:repo to prevent data loss."
  • Do NOT dispatch the sub-agent. Do NOT read session context. Do NOT proceed to Step 1.

If the output is empty, continue.

Capture commit baseline (for the Step 5 commit offer): BEFORE propagation, snapshot the repo's dirty set into a freshly mktemp'd file (NOT a fixed path — concurrent runs would collide, CR-004) and remember the generated path: BASELINE_REPO=$(mktemp); bash ${CLAUDE_PLUGIN_ROOT}/scripts/commit-candidates.sh snapshot . > "$BASELINE_REPO". Thread $BASELINE_REPO to Step 5 — do not hardcode the baseline filename there.

1. Gather Session Context

First, verify Python 3 is available — all helper scripts depend on it:

command -v python3 >/dev/null 2>&1 || { echo "ERROR: python3 not found in PATH — install python3 and retry."; exit 1; }
bash ${CLAUDE_PLUGIN_ROOT}/scripts/context-gather.sh

Combine with conversation history.

2. Build the Session-Change Summary

Read ${CLAUDE_PLUGIN_ROOT}/templates/session-change-summary.md for the canonical format. Produce a concrete summary following that template — name exact keys/values/paths, not vague "updated config" language.

3. Dispatch up-docs-propagate-repo

Invoke the sub-agent via the Agent tool with subagent_type: "up-docs:up-docs-propagate-repo" (the up-docs: prefix is required — plugin-defined agents are only addressable through their plugin namespace). The prompt has the session-change summary at the stable front, followed by any repo-specific context (CLAUDE.md ## Documentation section if present).

Read the full file on GitHub · 72 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. 4d ago First seen · 72 lines · 51 tokens per session scan A f0e09ee0f8d3

Subscribe to this mod's changes

repo is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (6 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 1,115 once invoked, about $0.0003 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-04.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens