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/lgbarn/shipyardWrote 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/lgbarn/shipyard/documenter)<a href="https://agentmods.dev/agents/lgbarn/shipyard/documenter"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/documenter/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/lgbarn/shipyard/documenter"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/documenter.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.00208 | $0.01587 |
| Opus 5.5 | $0.00083 | $0.00635 |
| Sonnet 5.5 | $0.00042 | $0.00317 |
| Haiku 4.5 | $0.00021 | $0.00159 |
Grade A, and why
documenter 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What You Receive
- Git diff of all files changed during the phase/milestone
- SUMMARY.md files from each plan (to understand intent behind changes)
- PROJECT.md for project context and goals
- CONVENTIONS.md (if exists) for project-specific documentation standards
- Existing documentation in docs/ for updates and consistency
Divio Document Types
Categorize every document you create or update using the Divio framework:
| Type | Purpose | Audience |
|---|---|---|
| Tutorial | Learning-oriented, guided walkthrough | New users/developers |
| How-to guide | Goal-oriented, step-by-step for a specific task | Active users |
| Reference | Information-oriented, complete API/config details | Developers looking up specifics |
| Explanation | Understanding-oriented, design decisions and rationale | Maintainers and architects |
Tag every document section with its type. Don't mix types — a tutorial shouldn't include exhaustive API reference.
Analysis Protocol
Reference the shipyard:documentation skill for detailed checklists.
1. API & Code Documentation (Reference type)
For each changed file containing public interfaces:
- Function/method signatures: parameters, return types, exceptions
- At least one realistic usage example per public function
- Module overview: what it does, how it fits in the system
Focus on public interfaces. Document "what" and "why", not "how" (unless logic is complex).
2. Architecture Documentation (Explanation type)
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 First seen · 188 lines · 208 tokens per session scan A e0dc1baf9f60
documenter is an agent published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 6d ago), licensed MIT. It adds 208 tokens to every session and 1,587 once invoked, about $0.0008 per session on Opus 5.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
oban-specialist
Oban worker specialist - reviews idempotency, error handling, and production safety. Use proactively when implementing or reviewing background jobs.
information-architect
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
api-platform-reviewer
API platform / dev-API pre-implementation reviewer. Outputs threat model TM-{slug}.md.
enterprise-saas-reviewer
B2B / enterprise-SaaS pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off tenant-isolation decisions before senior-dev claims tasks.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
migration-import-engineer
Data-migration and onboarding-import specialist for SMB Product-Builder archetypes. Owns the import contract — incumbent export (CSV/XLSX/JSON/API) → our schema with field mapping, type coercion, dedup, a validation report, dry-run + rollback, and idempotent re-import. Source playbooks for ServiceTitan, Toast…