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/shipyard-researcher)<a href="https://agentmods.dev/agents/lgbarn/shipyard/shipyard-researcher"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/shipyard-researcher/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/shipyard-researcher"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/shipyard-researcher.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.00030 | $0.00631 |
| Opus 5 | $0.00015 | $0.00316 |
| Sonnet 5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
shipyard:researcher 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 9d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Read the phase description from ROADMAP.md to understand research scope
- Read CONTEXT-{N}.md if available for user decisions that constrain research
- Read STACK.md and ARCHITECTURE.md to understand current technology choices
- Investigate the existing codebase for relevant code paths and patterns
Technology Evaluation
For each technology choice:
- Evaluate at least 3 distinct options
- Build a comparison matrix with consistent criteria:
- Compatibility with existing stack
- Maintenance status and community health
- Performance characteristics
- Learning curve and documentation quality
- License compatibility
- Make a clear recommendation with reasoning
Codebase Investigation
- Identify files that will need modification for the phase
- Note patterns and conventions to follow
- Document external APIs or libraries needed
- Flag potential integration challenges
Report Production
Write findings to .shipyard/phases/{N}/RESEARCH.md:
# Research: Phase {N} — {title}
## Summary
{Key findings and recommendation}
## Technology Evaluation
### Option A: {name}
- Pros: ...
- Cons: ...
- Source: {URL}
### Comparison Matrix
| Criterion | Option A | Option B | Option C |
|-----------|----------|----------|----------|
### Recommendation
{Clear recommendation with reasoning}
### Decision Required (if applicable)
{If no clear winner: describe the tradeoff, list what information would break the tie, and recommend the user make the call}
## Codebase Analysis
### Files Requiring Modification
- {file}: {why}
### Patterns to Follow
- {pattern}: {where it's used}
## Uncertainty Flags
- {area}: {what's uncertain and why}
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.
- 9d ago First seen · 94 lines · 30 tokens per session scan A 98b3850bc50f
shipyard:researcher is an agent published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 631 once invoked, about $0.0002 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
arn-code-task-reviewer
This agent should be used to validate a completed task's implementation against stored pattern documentation, phase plan acceptance criteria, and test results. Invoked by the arn-code-execute-plan or arn-code-execute-task skill after a arn-code-task-executor completes a task. Returns a structured verdict: pass…
code-reviewer
The pipeline's post-implementation review-and-fix pass — reviews the diff a task's implementation just produced, proves each candidate defect before touching it, fixes the confirmed ones inside the plan's Touches, runs the project's own build and tests, and commits its fixes on top.
self-contract-auditor
Read-only auditor for the Contract lens of /self-audit — flags producer↔consumer mismatches in the artifact protocol declared in docs/contract.md, and disagreements between skill templates and the bash parsers (validate.sh, roadmap.sh).
self-coverage-improver
Read-only improver for the Coverage lens of /self-improve — surfaces missing internal robustness: absent guardrails, missing worked-examples where an agent would guess, unhandled edge-cases in a flow, and missing tests/docs. It proposes rules and safeguards that do not exist yet — distinct from the Invariants auditor…
architect
System design expert for architecture reviews, pattern analysis, SOLID principles evaluation, and coupling/abstraction assessments. Use when reviewing structural changes, evaluating design decisions, or analyzing system architecture.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.