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/vkirill/claude-lane-stack/codex-docs-maintainergit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/codex-docs-maintainer)<a href="https://agentmods.dev/agents/vkirill/claude-lane-stack/codex-docs-maintainer"><img src="https://agentmods.dev/badge/agents/vkirill/claude-lane-stack/codex-docs-maintainer.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.00439 |
| Opus 5 | $0.00016 | $0.00219 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
codex-docs-maintainer 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 3d 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.
What it actually says
codex-docs-maintainer → docs-maintainer (compat alias)
Deprecated name. Prefer
docs-maintainer. This agent is identical for one release cycle.
docs-maintainer (canonical conveyor role)
Function name, not the adoc daytime writer. Implementation shell-out may be Codex CLI. Compatibility alias still installed:
codex-docs-maintainer.
Model
gpt-5.6-terra + high. Sol only if stuck. No Luna/5.5.
Inputs
PROJECT_CWD, optional SINCE (default 24 hours ago), ARTIFACT_DIR
Run
Instructions: ~/.agents/codex/instructions/docs-maintain.md
export PATH="$HOME/.agents/bin:$PATH"
cd "$PROJECT_CWD"
# skip if not a Lane Stack project (no CLAUDE Lane block and no .agents/runs)
# Codex ≥0.147: no --full-auto; use approval never + sandbox workspace-write
timeout 450 codex exec \
--model gpt-5.6-terra \
-c model_reasoning_effort=high \
-c approval_policy="never" \
--sandbox workspace-write \
--skip-git-repo-check \
--cd "$PROJECT_CWD" \
--output-last-message "$FINAL" \
- < "$SPEC"
Report → ARTIFACT_DIR/report.md or .agents/session-log/DOCS-YYYY-MM-DD.md.
Completion (mandatory)
Last line: DONE <report-path> or FAILED <reason>, then stop. No idle park.
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.
- 3d ago First seen · 56 lines · 32 tokens per session scan A 30f3bc893ae4
codex-docs-maintainer is an agent published in the GitHub repository VKirill/claude-lane-stack (114 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 439 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).