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/agents-mdgit 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.01089 | $0.01089 |
| Opus 5 | $0.00544 | $0.00544 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
shipyard AGENTS.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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipyard
Agent-driven plugin (v4.8.0) for structured project execution: idea → brainstorm → plan → build → ship.
Shipyard is authored as a Claude Code plugin (canonical source) and also ships a generated Codex plugin tree so Codex users can install it natively. The Claude Code artifacts are the single source of truth; the Codex tree is a build output (see "Codex support" below).
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
bash scripts/build-codex.sh # Regenerate the Codex plugin tree from canonical artifacts
bash scripts/check-codex-sync.sh # Verify the committed Codex tree matches the generator
shellcheck --severity=warning scripts/*.sh hooks/*.sh test/run.sh
Architecture
commands/ Slash commands (markdown + YAML frontmatter) — Claude Code
skills/ Auto-activating skills (skills/<name>/SKILL.md) — shared with Codex
agents/ Specialized subagents (markdown + YAML frontmatter) — Claude Code
scripts/ State management, version checks, Codex generator, cleanup utilities
hooks/ Plugin lifecycle hooks (SessionStart, TeammateIdle, TaskCompleted, Stop) — Claude Code
test/ BATS test suite + test_helper.bash
docs/ Protocols, guides, state schema, context engineering
.claude-plugin/ Claude Code plugin metadata (plugin.json, marketplace.json) — canonical
plugins/ Generated Codex plugin tree (plugins/shipyard/.codex-plugin/, skills/)
.agents/ Generated Codex marketplace manifest (.agents/plugins/marketplace.json)
.husky/ Pre-commit: check-versions.sh && check-codex-sync.sh && npm test
Codex support
Codex artifacts are generated from the canonical Claude Code artifacts — never hand-edited.
scripts/build-codex.shtransforms.claude-plugin/plugin.json+skills/into the Codex tree underplugins/shipyard/and.agents/plugins/marketplace.json.scripts/check-codex-sync.shregenerates into a temp dir and diffs against the committed tree; any drift fails CI. This is what keeps the Codex tree from drifting by hand.- Codex install:
codex plugin marketplace add lgbarn/shipyard, then enable the plugin. - Codex support is best-effort, not parity: skills run natively, but parallel subagent dispatch and lifecycle hooks degrade (see the PRD and the "Using Shipyard with Codex" guide).
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.
- 3d ago First seen · 82 lines · 1,089 tokens per session scan A 5b8eaa74fe19
shipyard AGENTS.md is an instructions file published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 1,089 tokens to every session, about $0.0054 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
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
chatgpt-cli CLAUDE.md
Instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
cetus AGENTS.md
Instructions for drewnekota/cetus, covering repository instructions and releases.
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
roamcode AGENTS.md
Instructions for burakgon/roamcode, covering repository instructions for coding agents, public-repository safety, stable release and ota contract, releasing a stable version and ota changes.