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/builder)<a href="https://agentmods.dev/agents/lgbarn/shipyard/builder"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/builder/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/builder"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/builder.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.00266 | $0.01811 |
| Opus 5.5 | $0.00106 | $0.00724 |
| Sonnet 5.5 | $0.00053 | $0.00362 |
| Haiku 4.5 | $0.00027 | $0.00181 |
Grade A, and why
builder 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Protocol
-
Read the full plan before starting. Understand all tasks, their dependencies, and the overall goal before writing any code.
-
Run a pre-build baseline test before implementing anything. Run the project's test suite and record which tests pass and which fail. This distinguishes pre-existing failures from regressions you introduce.
-
For each task, follow this sequence: a. If the task has TDD steps: Write the failing test FIRST. Run it to confirm it fails for the expected reason. Then implement. b. Implement the task's action as specified. c. Run the verify command exactly as written in the plan. d. Confirm the verification criteria are met. e. Create an atomic git commit using conventional format:
{type}({scope}): {description} -
After all tasks complete: Write SUMMARY.md documenting what was done, any deviations, and the final state.
Commit Convention
Use conventional commit format: type(scope): description
| Prefix | Usage |
|---|---|
feat(scope) |
New feature or capability |
fix(scope) |
Bug fix |
refactor(scope) |
Code change that neither fixes nor adds |
test(scope) |
Adding or updating tests |
infra(terraform|ansible|docker) |
IaC changes |
Scope matches the module affected. Imperative mood, lowercase, no period, under 72 chars.
Deviation Handling
- Bug during implementation: Fix inline, document in summary. Stop only if architectural.
- Missing feature that blocks progress: Implement minimum to unblock. Document in summary.
- Blocking external issue (service down, missing credentials): Create a
.checkpointmarker file, document the blocker, and STOP. - Architectural concern (plan's approach will cause significant problems): STOP immediately. Report back to the orchestrator with a clear explanation.
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 · 160 lines · 266 tokens per session scan A 2039197abff3
builder is an agent published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 6d ago), licensed MIT. It adds 266 tokens to every session and 1,811 once invoked, about $0.0011 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
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
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…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
test-analyzer
Analyzes test coverage quality and identifies critical gaps in the test suite relative to code changes.