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 commands/lgbarn/shipyard/simplifygit 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.00018 | $0.00665 |
| Opus 5 | $0.00009 | $0.00332 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
simplify 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:simplify - On-Demand Simplification Review
You are executing an on-demand simplification review. Follow these steps precisely.
Step 1: Parse Arguments
Extract from the command:
scope(optional): What to analyze. Accepts:- No argument / "current": Analyze uncommitted changes (
git diff+git diff --cached) - Diff range (e.g.,
main..HEAD): Analyze commits in range - Directory path (e.g.,
src/): Analyze all files in directory - "." or "all": Analyze all changed files vs main branch
- No argument / "current": Analyze uncommitted changes (
If no scope and no uncommitted changes exist, default to analyzing changed files against the main branch.
Step 2: Detect Context
- Check if
.shipyard/exists (optional — this command works anywhere). - If
.shipyard/config.jsonexists, readmodel_routing.simplificationfor model selection. - Otherwise, use default model: sonnet.
- Follow Worktree Protocol (see
docs/PROTOCOLS.md) — detect worktree context.
Step 3: Gather Scope
Based on the scope argument, collect the code to analyze:
- Current:
git diff+git diff --cached - Range:
git diff <range> - Directory: List and read all source files in directory
- Full codebase:
git diff main...HEAD
Step 4: Build Agent Context
Assemble context per Agent Context Protocol (see docs/PROTOCOLS.md):
- The diff/file content collected in Step 3
.shipyard/PROJECT.md(if exists)- Codebase docs per Codebase Docs Protocol (if
.shipyard/exists) - Working directory, current branch, and worktree status
Step 5: Dispatch Simplifier
Dispatch a simplifier agent (subagent_type: "shipyard:simplifier") with:
- Follow Model Routing Protocol — resolve model from
model_routing.simplification(default: sonnet) - max_turns: 10
- All context from Step 4
- Instruction: Review for cross-file duplication, unnecessary abstractions, dead code, complexity hotspots, and AI-generated bloat patterns
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 · 74 lines · 18 tokens per session scan A 99bcb8e0c558
simplify is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 665 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.