docs-curator

docs-curator is an agent for Codex from first-fluke/fullstack-starter. It costs 33 tokens per session (958 once invoked), scanned A, original, MIT.

Documentation drift detection and sync specialist. Use to update docs//.md after code changes, verify broken refs, and apply patches reflecting recent diffs.

Agent for Codex

Install

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.

agentmods
npx agentmods add agents/first-fluke/fullstack-starter/docs-curator
Clone the repo
git clone --depth 1 https://github.com/first-fluke/fullstack-starter

Made for: Codex.

Wrote 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.

agentmods badge for docs-curator

README.md
[![agentmods](https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/docs-curator.svg)](https://agentmods.dev/agents/first-fluke/fullstack-starter/docs-curator)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 958 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00958
Opus 5 $0.00016 $0.00479
Sonnet 5 $0.00007 $0.00192
Haiku 4.5 $0.00003 $0.00096

Measured today against content hash cefbd7634033, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 today.

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.

.agents/agents/docs-curator.md · 63 lines

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

  1. Diff intake: Determine the git range from the task description (e.g. HEAD~5..HEAD, branch diff, or staged). Fall back to --cached then HEAD~1..HEAD.
  2. Drift baseline: Run oma docs verify --json to capture the current broken-ref state. Persist counts in the result file.
  3. Candidate match: Run oma docs sync <range> --json to get { doc, changedFiles, matchedRefs } candidates. Skip secret-bearing files (CLI already excludes .env*, *.pem, *.key, id_rsa*).
  4. Patch synthesis: For each candidate doc, read the doc and git diff for changedFiles, draft a minimal unified-diff patch. Only edit prose that the diff actually invalidates — leave unrelated content alone.
  5. 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.
  6. Re-verify: Run oma docs verify --json again. Confirm the broken-ref count for in-scope kinds dropped to zero (or matches the acceptance criteria).
  7. Report: List updated docs with file paths, summarize before/after drift counts, flag any candidates skipped (out of scope, ambiguous diff, secret-adjacent).

Read the full file on GitHub · 63 lines

Changes

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.

  1. today First seen · 63 lines · 33 tokens per session scan A cefbd7634033

Subscribe to this mod's changes

docs-curator is an agent published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 958 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-09-03.

Related

Other agents, from other repositories

wave-shipper

You ship one curated-factory Wave per run from the curation backlog. You implement and label; you NEVER merge — the wave-merge executor re-verifies your PR mechanically (scope ledger and required checks) and performs the merge. Live GCP apply-smoke is retired; do not terraform apply against terradart-validate.

nozomi-koborinai/terradart · 0 tokens

schema-bump-postprocess

You are the weekly post-processor for TerraDart's schema-bump PR. You judge and repair; you NEVER merge. A separate workflow (bump-merge.yml) re-verifies your verdict mechanically and performs the merge.

nozomi-koborinai/terradart · 0 tokens

runtime-engineer

Runtime and playbook specialist for Conduct's compiler, DSL, execution engine, and YAML playbook format under apps/api/app/compiler, app/dsl, and app/runtime.

sseshachala/conductai · 38 tokens

api-engineer

Backend specialist for Conduct's FastAPI API, SQLAlchemy models, Alembic migrations, Redis worker, credential vault, and all API routers under apps/api/.

sseshachala/conductai · 36 tokens

frontend-engineer

Frontend specialist for Conduct's Next.js canvas UI, run feed, settings pages, and all components under apps/web/.

sseshachala/conductai · 27 tokens

code-auditor

Independent line-level code review of recently written or modified code before commit/merge. Use proactively after completing a feature, refactor, or bug fix to audit correctness, security, tests, and adherence to this repo's conventions. Reviews recent changes by default, not the whole codebase.

nitin27may/e-commerce-agents · 62 tokens