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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/docs-curator)<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/docs-curator"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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/first-fluke/fullstack-starter/docs-curator"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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.00825 |
| Opus 5.5 | $0.00013 | $0.00330 |
| Sonnet 5.5 | $0.00007 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
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
100% identical to docs-curator — 0 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 — 44 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:
- Use the injected claim path and task/run/session identity from
.agents/skills/_shared/runtime/result-contract.md. Human-readable reports useresult-{agentId}-{taskId}-{runId}-{sessionId}.md. - Include: status, summary, files changed, acceptance criteria checklist
Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.
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).
Auto-Write Authority
A scoped user edit request or assigned implementation task authorizes those corrections, regardless of entry point. Review-only requests produce findings or proposals. Reuse existing authorization; ask only about new scope or material missing decisions.
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 Changed · -19 lines 165b5e38282c
- 1mo ago Changed 732ab0e49615
- 1mo ago First seen · 63 lines · 33 tokens per session scan A cefbd7634033
docs-curator is an agent published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 825 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to docs-curator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
system-architect
Runs one bounded deep dive on a single risky component of a system design and returns options, failure modes, and a justified recommendation. Use during a design session when a component needs expert depth beyond the main thread's budget.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
codebase-scout
Explores codebase structure, affected files, blast radius, related tests, and local conventions for a focused topic. Use when review or planning needs structural lookup without bloating main context.
pr-reviewer
Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.