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 skills/lgbarn/shipyard/shipyard-mapnpx skills add lgbarn/shipyard --skill shipyard-mapgit 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/skills/lgbarn/shipyard/shipyard-map)<a href="https://agentmods.dev/skills/lgbarn/shipyard/shipyard-map"><img src="https://agentmods.dev/badge/skills/lgbarn/shipyard/shipyard-map.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.00088 | $0.00468 |
| Opus 5 | $0.00044 | $0.00234 |
| Sonnet 5 | $0.00018 | $0.00094 |
| Haiku 4.5 | $0.00009 | $0.00047 |
Grade A, and why
shipyard-map 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.
What it actually says
Mapping a codebase (Codex inline-sequential)
This is the mapper role from Shipyard's /shipyard:init and /shipyard:map flows, adapted
for Codex. In Claude Code, mapper runs as four parallel subagents (technology,
architecture, quality, concerns). Codex has no parallelism, so you cover the four focus
areas sequentially in this one context.
You are an analysis-only role. You MUST NOT modify any code — you read, analyze, and document. Bash is for discovery only (line counts, dependency checks, git history), never for changing files.
Degradation note: the four focus areas run one after another instead of in parallel, so a full map takes longer. The output quality is the same — only the wall-clock differs.
Focus areas (run each in turn)
- Technology →
STACK.md— languages, frameworks, build tooling, dependencies. - Architecture →
ARCHITECTURE.md— module boundaries, data flow, why the code is structured the way it is (not just a file listing). - Quality →
TESTING.md/CONVENTIONS.md— test posture, coverage gaps, conventions. - Concerns →
CONCERNS.md— where the real risks hide: fragile areas, tech debt, security-sensitive paths.
Rules
- Cite every finding with at least one repo-relative file path (e.g.
scripts/state-read.sh). Never assert without evidence. Never use absolute paths. - Merge, don't overwrite existing docs — update and date them rather than replacing.
- Surface insight, not surface-level inventory: explain why, and where the risks are.
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 · 35 lines · 88 tokens per session scan A 3e60c591db08
shipyard-map is a skill published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 468 once invoked, about $0.0004 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 skills, from other repositories
cco-export
Export context report as Markdown or HTML.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-deck
Generate slide deck presentations from briefs — use when you need slides, pitch decks, or visual summaries.
add-pdf-report
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
add-onedrive
Adds OneDrive for Business connector to a Power Apps code app. Use when uploading, downloading, listing, or managing files in OneDrive.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.