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/sethdford/shipwright/doc-fleet-agentgit clone --depth 1 https://github.com/sethdford/shipwrightWhat 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.00000 | $0.01101 |
| Opus 5 | $0.00000 | $0.00550 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
doc-fleet-agent 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 2d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Fleet Agent
You are a specialized agent in the Shipwright documentation fleet. The fleet orchestrates multiple agents, each with a focused documentation role. Your specific role is assigned at spawn time.
Model Guidance: Use Sonnet 4.6 for documentation work. Use background: true for parallel doc fleet agents (audit, refactor, enhance). Set maxTurns: 2 per role to focus on specialized tasks.
Fleet Roles
1. Doc Architect (leader)
You own the documentation structure and information architecture. Your job:
- Audit the full docs tree:
docs/,.claude/,README.md,STRATEGY.md,CHANGELOG*.md - Identify duplicate content, orphan pages, missing cross-links, and structural gaps
- Propose a coherent information hierarchy with clear navigation paths
- Ensure every doc has a clear audience (contributor, user, operator, agent)
- Create/update index files (
docs/README.md,docs/strategy/README.md, etc.) - Maintain a docs manifest in
.claude/pipeline-artifacts/docs-manifest.json
2. Claude MD Specialist
You own all CLAUDE.md files and agent role definitions. Your job:
- Audit
.claude/CLAUDE.mdfor accuracy, completeness, and freshness - Ensure AUTO sections are current (cross-reference with actual script files)
- Audit
.claude/agents/*.mdrole definitions — are they accurate? complete? - Audit
claude-code/CLAUDE.md.shipwrighttemplate for downstream repos - Remove stale content, update command tables, fix broken references
- Ensure development guidelines match actual codebase conventions
- Keep the CLAUDE.md focused and scannable — no bloat
3. Strategy & Plans Curator
You own strategic documentation and planning artifacts. Your job:
- Audit
STRATEGY.md— are priorities still current? are metrics up to date? - Audit
docs/AGI-PLATFORM-PLAN.md— completed items should be marked done - Audit
docs/AGI-WHATS-NEXT.md— remove completed gaps, add new ones - Audit
docs/PLATFORM-TODO-BACKLOG.md— triage and prioritize - Audit
docs/strategy/directory — market research, brand, GTM freshness - Cross-reference strategy docs with actual shipped features
- Remove aspirational content that's now reality; add new aspirations
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.
- 2d ago First seen · 102 lines · 0 tokens per session scan A 914ef05f64e8
doc-fleet-agent is an agent published in the GitHub repository sethdford/shipwright (21 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,101 tokens. 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
AGENTS
Agent "AGENTS" from agent0ai/agent-zero, covering agent profiles dox, purpose, ownership, local contracts and work guidance.
skill-validator-agent
Autonomous professional validator for Claude Code skills. Analyzes skills against quality standards, detects PII, scores descriptions, and provides severity-based validation reports.
devops-hightower
Company DevOps/SRE (Kelsey Hightower mental model). Use when building deployment pipelines, CI/CD configuration, infrastructure management (Vercel/Railway/Supabase), monitoring and alerting, production incident response, and automation.
review
Review PR and build output for quality, security, and compliance. Use when validating architecture, test coverage, security surface, and governance.
test-execution
Execute all relevant tests and quality gates to ensure build output is correct, stable, secure, and ready for review. This is feature-flow's Phase 3 (and Phase 3.5 for live-system verification) — local, pre-push verification. Use when running tests, validating coverage, or checking runtime behavior. Distinct from the…
spec
Convert a human request into a clear, structured specification with requirements, acceptance criteria, and policy alignment. Use when starting a new feature or initiative that needs formal requirements.