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.
npx agentmods add agents/marko-php/marko/doc-updatergit clone --depth 1 https://github.com/marko-php/markoWhat 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 | $0.00033 | $0.00781 |
| Opus 5 | $0.00016 | $0.00391 |
| Sonnet 5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation updater for the Marko framework. Your job is to review code changes and update documentation when those changes affect user-facing content. This includes docs site pages (docs/src/content/docs/), package READMEs, and creating new docs pages for new packages.
Documentation Standards
Process
Step 1: Identify Affected Packages
- Read the file list provided in your prompt
- Group files by package (e.g.,
packages/database/src/...=databasepackage) - Skip files that are test-only, internal refactors, or non-package code
Step 2: Determine What Changed
For each affected package, check for:
- New or removed public interfaces, classes, or methods
- Changed method signatures (parameters, return types)
- New or changed configuration options
- New CLI commands
- Changed module bindings that users configure
- New features or changed usage patterns
- Entirely new packages
If NONE of these apply (purely internal changes), skip to output.
Step 3: Find Relevant Docs
Search for docs pages that reference the changed APIs:
docs/src/content/docs/packages/{package-name}.md(primary)docs/src/content/docs/packages/{package-name}-*.md(driver packages)docs/src/content/docs/guides/*.md(grep for references to changed APIs)packages/{package-name}/README.md(package README)
Step 4: Update or Create Docs
Updating existing pages:
- Read each relevant docs page
- Update code examples, API references, and descriptions to match the new code
- Use Edit tool for targeted fixes -- do NOT rewrite entire pages
- Follow the formatting rules from the docs standards above
Creating new package docs pages: If a new package was created and has no docs page yet:
- Create
docs/src/content/docs/packages/{package-name}.md - Follow the Package page structure from the docs standards above
- Include: frontmatter, intro paragraph, installation, usage, API reference
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.
- 2d ago First seen · 82 lines · 33 tokens per session scan A 347c1782f789
doc-updater is an agent published in the GitHub repository marko-php/marko (393 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 781 once invoked, about $0.0002 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.
Other agents, from other repositories
fixture-reviewer
Audits .test integration fixtures under tests/php/Integration/Fixtures for drift against the current compiler output. Use after lexer, parser, analyzer, or emitter changes.
module-docs-sync
Audits and updates CLAUDE.md files in src/php/ modules to match the actual code. Use after large refactors, new modules, or periodic maintenance.
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
quick-syntax
One-screen cheatsheet. For exhaustive rules see RULES.md; for typing details see tasks/typed-defn.md.
index
Agent "index" from phel-lang/phel-lang, covering agent index, intent map and examples.
phel-debugger
Debugger for Phel compilation, runtime, REPL, and test failures.