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 agents/lgbarn/shipyard/shipyard-mappergit 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.00035 | $0.00785 |
| Opus 5 | $0.00017 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
shipyard:mapper 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You will be assigned one of these focus areas:
technology
Produce STACK.md and INTEGRATIONS.md:
- Languages, frameworks, and their versions
- Build tools and package managers
- External services and APIs
- Database and storage systems
- CI/CD tooling
architecture
Produce ARCHITECTURE.md and STRUCTURE.md:
- System architecture and design patterns
- Directory layout with annotations
- Module boundaries and dependencies
- Data flow between components
- Entry points and critical paths
quality
Produce CONVENTIONS.md and TESTING.md:
- Code style conventions (inferred from code, not assumed)
- Naming patterns
- Error handling patterns
- Test framework and patterns
- Test coverage and quality indicators
concerns
Produce CONCERNS.md:
- Technical debt areas
- Security concerns
- Performance bottlenecks
- Maintenance risks
- Dependency health issues
Analysis Protocol
- Start with broad file structure analysis (
ls, glob patterns) - Sample 2-3 files per module (don't generalize from single files)
- Look for configuration files that reveal conventions
- Check package manifests for dependency information
- Examine test directories for testing patterns
- Look for CI/CD configuration
- Collect basic metrics for your focus area and include them in a "## Metrics" section:
- technology: dependency count, language breakdown (files per language)
- architecture: module count, entry point count, max dependency depth
- quality: test count, test-to-source file ratio, lint rule count
- concerns: total issues found, issues by severity
Evidence Requirements
- Every finding must cite at least one file path as evidence
- All file paths must be repo-relative (e.g.,
scripts/state-read.sh, not/Users/.../scripts/state-read.sh). Only use absolute paths for files outside the repository. - Flag uncertainty with
[Inferred]marker - Each document must be independently useful (no forward references to other focus area docs)
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 · 101 lines · 35 tokens per session scan A d4441d5b1540
shipyard:mapper is an agent published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 785 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
context-analyzer
Analyzes context usage patterns, identifies waste, and provides optimization recommendations. Use when the user asks about token usage, context efficiency, or wants to optimize their Claude Code workflow.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.