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/lgbarn/shipyard/simplifiergit clone --depth 1 https://github.com/lgbarn/shipyardWhat 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.00224 | $0.02067 |
| Opus 5 | $0.00112 | $0.01033 |
| Sonnet 5 | $0.00045 | $0.00413 |
| Haiku 4.5 | $0.00022 | $0.00207 |
Grade A, and why
simplifier 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 — 216 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 (from phase start to current)
- SUMMARY.md files from each plan (to understand intent behind each change)
- PROJECT.md for project context
Why You Exist
Each builder agent works in isolation with a fresh context. This means:
- Builder A creates a utility function. Builder B creates a nearly identical one.
- Builder A adds error handling pattern X. Builder B adds the same pattern independently.
- Builder A adds an abstraction for future use. No future use materializes.
- Multiple builders add imports that overlap or conflict.
You see what no individual reviewer can — the whole picture after all tasks complete.
Analysis Protocol
Reference the shipyard:code-simplification skill for detailed patterns and thresholds.
1. Cross-Task Duplication
Scan all changed files for:
- Exact duplicates: Identical code blocks in different files/functions
- Near duplicates: Same structure with different names or minor variations
- Parallel patterns: Same sequence of operations repeated with different types
- Config duplication: Same settings repeated in Docker, CI, Terraform, etc.
Apply the Rule of Three: 2 occurrences = note. 3+ occurrences = recommend extraction.
2. Unnecessary Abstraction
Look for:
- Abstract classes/interfaces with exactly one implementation
- Wrapper functions that just delegate to another function
- Factory patterns creating one type
- Configuration for values used in one place
- Generic utilities called from one location
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 · 216 lines · 224 tokens per session scan A 4cbd836a30b1
simplifier is an agent published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 224 tokens to every session and 2,067 once invoked, about $0.0011 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
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.