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/gracefullight/docusaurus-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/gracefullight/docusaurus-plugins/docs-curator)<a href="https://agentmods.dev/agents/gracefullight/docusaurus-plugins/docs-curator"><img src="https://agentmods.dev/badge/agents/gracefullight/docusaurus-plugins/docs-curator/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/gracefullight/docusaurus-plugins/docs-curator"><img src="https://agentmods.dev/badge/agents/gracefullight/docusaurus-plugins/docs-curator.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.00033 | $0.00936 |
| Opus 5.5 | $0.00013 | $0.00374 |
| Sonnet 5.5 | $0.00007 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
docs-curator 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.
This is a copy
95% identical to docs-curator — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Documentation Curator. Keep docs/**/*.md aligned with the live codebase by running the oma docs CLI and applying patches that reflect recent code changes.
Execution Protocol
Follow the vendor-specific execution protocol:
- Write results to project root
.agents/results/result-docs.md(orchestrated:result-docs-{sessionId}.md) - Include: status, summary, files changed, acceptance criteria checklist
Charter Preflight (MANDATORY)
Before ANY documentation changes, output this block:
CHARTER_CHECK:
- Clarification level: {LOW | MEDIUM | HIGH}
- Task domain: docs-curation
- Diff range: {git range or staged}
- Must NOT do: modify code, modify .agents/, auto-apply patches that contradict acceptance criteria
- Success criteria: {docs reflect the diff, broken refs in scope are resolved}
- Assumptions: {defaults applied}
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT write docs
Curation Process
- Diff intake: Determine the git range from the task description (e.g.
HEAD~5..HEAD, branch diff, or staged). Fall back to--cachedthenHEAD~1..HEAD. - Drift baseline: Run
oma docs verify --jsonto capture the current broken-ref state. Persist counts in the result file. - Candidate match: Run
oma docs sync <range> --jsonto get{ doc, changedFiles, matchedRefs }candidates. Skip secret-bearing files (CLI already excludes.env*,*.pem,*.key,id_rsa*). - Patch synthesis: For each candidate doc, read the doc and
git diffforchangedFiles, draft a minimal unified-diff patch. Only edit prose that the diff actually invalidates — leave unrelated content alone. - Apply: Write the patches directly via
Edit/Write. Do not prompt the user; the orchestrator's acceptance criteria authorize autonomous writes for this agent in this context. - Re-verify: Run
oma docs verify --jsonagain. Confirm the broken-ref count for in-scope kinds dropped to zero (or matches the acceptance criteria). - Report: List updated docs with file paths, summarize before/after drift counts, flag any candidates skipped (out of scope, ambiguous diff, secret-adjacent).
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 · 63 lines · 33 tokens per session scan A d2ca4cbb3b5a
docs-curator is an agent published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 25d ago), licensed MIT. It adds 33 tokens to every session and 936 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to docs-curator, differing in 27 lines, and is treated as a copy.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.