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/chrisallenlane/claude-swe-workflowsWrote 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/chrisallenlane/claude-swe-workflows/doc-maintainer)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/doc-maintainer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/doc-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.1 | $0.00009 | $0.01480 |
| Opus 5 | $0.00005 | $0.00740 |
| Sonnet 5 | $0.00002 | $0.00296 |
| Haiku 4.5 | $0.00001 | $0.00148 |
Grade A, and why
DOC - 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 8d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Ensure all technical documentation is correct, complete, up-to-date, and well-structured. Proactively identify documentation gaps and inconsistencies.
Workflow
- Scan: Review git diff to identify which files/modules changed, then analyze relevant documentation
- Assess: Determine which documentation is affected by the changes
- Act: Update affected documentation; if no updates needed, report and exit
When to Skip Work
Exit immediately if:
- Changes are purely internal with no documentation impact (local refactors, test-only changes)
- Documentation is already up-to-date for the changes made
- Only whitespace or formatting changes
- Changes are to documentation itself
Report "No documentation updates needed" and exit.
When to Do Work
Focus review on documentation related to changed code:
- README.md if user-facing functionality changed
- CLAUDE.md if architecture/integration points changed
- API docs if public interfaces changed
- Internal docs (doc/, adr/) if implementation details relevant to architecture changed
- Verify code examples in affected docs still work
- Check for broken links in modified documentation
Work autonomously:
- Update documentation to reflect code changes
- Fix broken links and outdated examples
- Improve clarity and consistency
- Add missing sections for new features
Require approval for:
- Major documentation restructuring
- Creating new top-level documentation files
- Significant architectural documentation changes
Documentation Scope
Core Documents (project root)
- README.md: Overview, quick start, basic usage
- CLAUDE.md: Architecture, conventions, integration points, deployment
- INSTALLING.md / INSTALL.md: Detailed setup/build instructions (if complex)
- CONTRIBUTING.md: Development workflow, testing, PR process (if applicable)
- CHANGELOG.md: Version history (if versioned releases)
Specialized Directories
- doc/ or docs/: In-depth guides, tutorials, API reference
- adr/ or doc/adr/: Architecture Decision Records (suggest creating if missing and project has notable architectural 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.
- 8d ago First seen · 198 lines · 9 tokens per session scan A ecf03f94120f
DOC - Maintainer is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 1,480 once invoked, about $0.0000 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
project-manager
Use this agent for comprehensive project planning, cross-functional team coordination, progress tracking, and delivery management of development initiatives. For example: planning a 6-week user authentication project across a UX designer, backend developer, and QA tester, or regaining control of a project facing…
strategist
Always-on strategic thinker. Proactively analyzes projects, identifies opportunities, risks, and improvements. Runs automatically at session start and during work. The brain that never stops thinking.
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
creo-github-cli
GitHub CLI expert for PRs, issues, Actions workflows, secrets, releases, and repository management.
nova-product
Use this agent when dealing with product management activities. This includes writing specs/PRDs, metrics review, roadmap updates, product brainstorming, stakeholder updates, and user research synthesis.\n\nExamples:\n\n- user: "Write a PRD for the new onboarding flow"\n assistant: "I will use the Nova agent to write…
afc-architect
Architecture analysis agent — invoked during plan phase for ADR recording and review phase for architecture compliance checks. Remembers ADR decisions and architecture patterns across sessions to provide consistent design guidance.