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.
git clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWrote 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.
[](https://agentmods.dev/commands/closedloop-ai/claude-plugins/update-documentation)<a href="https://agentmods.dev/commands/closedloop-ai/claude-plugins/update-documentation"><img src="https://agentmods.dev/badge/commands/closedloop-ai/claude-plugins/update-documentation/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.
<a href="https://agentmods.dev/commands/closedloop-ai/claude-plugins/update-documentation"><img src="https://agentmods.dev/badge/commands/closedloop-ai/claude-plugins/update-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02862 |
| Opus 5.5 | $0.00000 | $0.01145 |
| Sonnet 5.5 | $0.00000 | $0.00572 |
| Haiku 4.5 | $0.00000 | $0.00286 |
Grade A, and why
update-documentation 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 8d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
Arguments
$ARGUMENTS
| Argument | Description |
|---|---|
--dry-run |
Show what would be changed without modifying files |
--plugin <name> |
Only update documentation for specified plugin |
--changelog-only |
Skip README verification, only update changelog |
--readme-only |
Skip changelog update, only verify/fix READMEs |
| (plain text) | Use as description for changelog entry |
Execution Modes
Determine the execution mode before starting:
| Flag | Steps to Run |
|---|---|
| (none) | All steps: 1 → 2 → 3 → 4 → 5 → 6 |
--changelog-only |
Steps 1 → 2 → 3 → 4 → 6 (skip README verification) |
--readme-only |
Steps 1 → 5 → 6 (skip changelog, verify READMEs for all changed plugins) |
Path Mappings
Plugin Paths
| Path | Plugin |
|---|---|
plugins/bootstrap/ |
bootstrap |
plugins/code/ |
code |
plugins/closedloop-core/ |
closedloop-core |
plugins/vibe/ |
vibe |
plugins/code-review/ |
code-review |
plugins/judges/ |
judges |
plugins/platform/ |
platform |
plugins/self-learning/ |
self-learning |
Ignored Paths
.claude/at project root- Paths outside
plugins/(root README.md, CLAUDE.md, .gitignore, etc.)
Changelog Format
The root CHANGELOG.md uses a single file with plugin-scoped sections in a flat, newest-first list. There is no ## [Unreleased] / ## [Releases] separator: every plugin entry is treated as released when merged to main. New entries are inserted at the top of the list.
# Changelog
All notable changes to the claude-plugins project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Entries are listed newest-first; each plugin section is treated as released when merged to `main`.
### code v1.1.0
#### Added
- New `code-reviewer` agent for language-agnostic code review
### judges v1.0.1
#### Fixed
- Fixed scoring normalization in KISS judge
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.
- 8d ago Changed · +2 lines 9509573f2dab
- 1mo ago First seen · 290 lines · 0 tokens per session scan A 9913a9465ede
update-documentation is a command published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,862 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.
Other commands, from other repositories
doc-changelog
Generation and maintenance of the project changelog.
release
Cut a release for one plugin, or for every plugin with changes worth releasing.
sync-ecosystem
Detect API changes, sync satellite repos, and publish releases.
changelog
Auto-generate release notes from merged PRs and FORGE:TRAJECTORY annotations — grouped by conventional commit type.
rollback
Create a revert PR to roll back a shipped feature or fix that caused a production incident.
ops-gitflow
Manage the GitFlow branching model: init, feature, release and hotfix branches.