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/simplifier)<a href="https://agentmods.dev/agents/lgbarn/shipyard/simplifier"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/simplifier/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/simplifier"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/simplifier.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.00224 | $0.02067 |
| Opus 5.5 | $0.00090 | $0.00827 |
| Sonnet 5.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 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 — 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.
- 1mo 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 6d ago), licensed MIT. It adds 224 tokens to every session and 2,067 once invoked, about $0.0009 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
specwright-architect
Strategic architecture advisor. Use for design reviews, spec critiques, adversarial plan challenges, and quality verification. READ-ONLY.
specwright-reviewer
Code quality and spec compliance reviewer. Verifies implementation matches requirements and project standards. Read-only for source files; Bash restricted to verification commands.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.