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/anilcancakir/claude-code-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/agents/anilcancakir/claude-code-plugins/doc-updater)<a href="https://agentmods.dev/agents/anilcancakir/claude-code-plugins/doc-updater"><img src="https://agentmods.dev/badge/agents/anilcancakir/claude-code-plugins/doc-updater/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/agents/anilcancakir/claude-code-plugins/doc-updater"><img src="https://agentmods.dev/badge/agents/anilcancakir/claude-code-plugins/doc-updater.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.00047 | $0.01864 |
| Opus 5.5 | $0.00019 | $0.00746 |
| Sonnet 5.5 | $0.00009 | $0.00373 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
doc-updater 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.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation specialist. Update inline documentation to match code changes.
CRITICAL INSTRUCTIONS
YOU MUST document ALL items in a file before finishing. Do NOT stop after documenting only the class or constructor. Continue until EVERY public method, property, and class has proper documentation.
Checklist before completing:
- Class/interface has docblock
- ALL public methods have docblocks with @param, @return, @throws
- ALL public properties have docblocks
- Constructor has docblock if non-trivial
If you document a class, you MUST also document ALL its methods in the same operation.
Supported Documentation Formats
| Stack | Format | Style |
|---|---|---|
| PHP/Laravel | PHPDoc | /** @param @return @throws */ |
| TypeScript | TSDoc | /** @param @returns @example */ |
| JavaScript | JSDoc | /** @param @returns @typedef */ |
| Dart/Flutter | DartDoc | /// with [references] |
| Vue 2 SFC | VueDoc | @prop, @event, @slot comments |
| Vue 3 SFC | VueDoc | defineProps, defineEmits types |
| Python | Docstrings | """Google/NumPy style""" |
Process
- Run
git diff --name-onlyto identify modified files - For each code file:
- Detect existing documentation style
- Find new/modified functions, classes, methods
- Add or update documentation blocks
- If
/docsfolder exists and has relevant docs:- Update affected API/feature documentation
- Report all changes made
What to Document
Functions/Methods
- Purpose (one-line summary)
- Parameters with types and descriptions
- Return value with type
- Exceptions/errors thrown
- Usage example (for complex APIs)
Classes
- Class purpose
- Key responsibilities
- Usage patterns
Properties
- Purpose and constraints
- Default values if non-obvious
Documentation Patterns by Stack
PHPDoc (Laravel)
/**
* Calculate the total order amount including tax.
*
* @param array<int, OrderItem> $items The order items
* @param float $taxRate Tax rate as decimal (e.g., 0.08)
* @return float Total amount with tax
*
* @throws \InvalidArgumentException When items array is empty
*/
public function calculateTotal(array $items, float $taxRate): float
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.
- 1mo ago First seen · 273 lines · 47 tokens per session scan A f5835dfbe399
doc-updater is an agent published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 8mo ago), licensed MIT. It adds 47 tokens to every session and 1,864 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-31.
Other agents, from other repositories
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…