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 instructions/lgbarn/shipyard/claude-mdgit 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/instructions/lgbarn/shipyard/claude-md)<a href="https://agentmods.dev/instructions/lgbarn/shipyard/claude-md"><img src="https://agentmods.dev/badge/instructions/lgbarn/shipyard/claude-md.svg" alt="Measured on agentmods" 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 | $0.00611 | $0.00611 |
| Opus 5 | $0.00305 | $0.00305 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
shipyard CLAUDE.md 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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipyard
Claude Code plugin (v4.5.0) for structured project execution: idea → brainstorm → plan → build → ship.
Commands
npm test # Full BATS test suite
npm run test:fast # Unit tests only (bats --filter-tags unit)
npm run test:ci # Parallel execution (4 jobs)
bash scripts/check-versions.sh # Verify version sync across files
shellcheck --severity=warning scripts/*.sh hooks/*.sh test/run.sh
Architecture
commands/ 27 slash commands (markdown + YAML frontmatter)
skills/ 19 auto-activating skills (skills/<name>/SKILL.md)
agents/ 10 specialized agents (markdown + YAML frontmatter)
scripts/ State management, version checks, cleanup utilities
hooks/ Plugin lifecycle hooks (SessionStart, TeammateIdle, TaskCompleted, Stop)
test/ BATS test suite + test_helper.bash
docs/ Protocols, guides, state schema, context engineering
.claude-plugin/ Plugin metadata (plugin.json, marketplace.json)
.husky/ Pre-commit: check-versions.sh && npm test
Version Sync
Four files must have matching version numbers. scripts/check-versions.sh enforces this (also runs in pre-commit hook and CI).
package.json.claude-plugin/plugin.json.claude-plugin/marketplace.jsonCHANGELOG.md(top entry)
Conventions
- Files/dirs: kebab-case
- Commits: conventional format —
feat:,fix:,chore:,build:,shipyard(phase-N): - Bash scripts:
set -euo pipefail, ShellCheck compliant (--severity=warning) - Skills: auto-discovered from
skills/*/SKILL.md— no manual registration - Agents: model values are
opus,sonnet,haiku, orinherit - Adding components: see CONTRIBUTING.md
Gotchas
- Pre-commit hook runs
check-versions.sh && npm test— both must pass .shipyard/is gitignored — local project state only, never committed- jq >= 1.6 required —
state-read.shexits code 3 if missing - Symlinked
.shipyard/is rejected (prevents writes outside project) - Team locking uses directory-based locks at
${TMPDIR}/shipyard-state-${hash}.lock - CI matrix tests on macOS, Ubuntu, and Windows (WSL); ShellCheck + version check run on Ubuntu only
- PR version bump enforced — CI rejects PRs where package.json version <= main branch version
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.
- 5d ago First seen · 56 lines · 611 tokens per session scan A 75e189a62feb
shipyard CLAUDE.md is an instructions file published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 611 tokens to every session, about $0.0031 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 instructions, from other repositories
super-token-saver CLAUDE.md
Claude Code instructions for ww-w-ai/super-token-saver, covering claude.md, what this is, architecture, two transcript sources, one pipeline and one repo, two hosts.
specwright AGENTS.md
AGENTS.md instructions for Obsidian-Owl/specwright, covering specwright, workflow, anchor documents, architecture and operator notes.
specwright CLAUDE.md
Claude Code instructions for Obsidian-Owl/specwright, a project described as: Craft quality software with AI discipline. Spec-driven development plugin for Claude Code and Opencode — quality gates, adversarial testing, and evidence capture.
specwright aikido_rules.instructions.md
Aikido MCP Security Rules.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.