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 commands/lgbarn/shipyard/mapgit 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.00016 | $0.01674 |
| Opus 5 | $0.00008 | $0.00837 |
| Sonnet 5 | $0.00003 | $0.00335 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:map - On-Demand Codebase Analysis
You are executing on-demand codebase analysis. Follow these steps precisely.
Step 1: Parse Arguments
Extract from the command:
focus(optional): Analysis focus area. Accepts:- No argument / "all": Run all 4 focus areas in parallel (dispatches 4 mapper agents)
- "technology": Map technology stack — languages, frameworks, dependencies, build tools (produces STACK.md + INTEGRATIONS.md)
- "architecture": Map system architecture — patterns, layers, boundaries, data flow (produces ARCHITECTURE.md + STRUCTURE.md)
- "quality": Map code quality — conventions, testing, patterns (produces CONVENTIONS.md + TESTING.md)
- "concerns": Map technical debt — outdated deps, security risks, performance issues (produces CONCERNS.md)
Step 2: Detect Context
- Check if
.shipyard/exists (optional — this command works anywhere). - If
.shipyard/config.jsonexists, readmodel_routing.mappingfor model selection andcodebase_docs_pathfor the output directory. - Otherwise, use default model: sonnet and default
codebase_docs_path:.shipyard/codebase. - Follow Worktree Protocol (see
docs/PROTOCOLS.md) — detect worktree context. - Store the resolved
codebase_docs_pathfor use in Steps 3 and 5.
Step 2a: Team or Agent Dispatch
Detection: Check the SHIPYARD_TEAMS_ENABLED environment variable (exported by scripts/team-detect.sh). This variable is set to true when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Prompt (conditional): If SHIPYARD_TEAMS_ENABLED=true, use AskUserQuestion with exactly two options:
- "Team mode (parallel teammates)" — uses TeamCreate/TaskCreate/SendMessage/TeamDelete lifecycle
- "Agent mode (subagents)" — uses standard Task dispatch (current behavior)
Question text: "Teams available. Use team mode (parallel teammates) or agent mode (subagents)?"
Silent fallback: If SHIPYARD_TEAMS_ENABLED is false or unset, silently set dispatch_mode to agent with no prompt (zero overhead).
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.
- 2d ago First seen · 133 lines · 16 tokens per session scan A cb1a0883a844
map is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,674 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.