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/issuesgit 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.00008 | $0.00659 |
| Opus 5 | $0.00004 | $0.00329 |
| Sonnet 5 | $0.00002 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
issues 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:issues - Issue Tracking
You are executing the Shipyard issue tracking workflow. Follow these steps precisely.
Step 1: Check State Exists
Check if .shipyard/ directory exists.
- If it does not exist:
Display:
"No Shipyard project detected. Run
/shipyard:initto get started." Stop here.
Step 2: Ensure ISSUES.md Exists
Check if .shipyard/ISSUES.md exists.
- If it does not exist, create it with this template:
# Shipyard Issues
Deferred enhancements and non-blocking findings tracked across sessions.
## Open Issues
| ID | Severity | Source | Description | Date |
|----|----------|--------|-------------|------|
## Resolved Issues
| ID | Description | Resolved | Resolution |
|----|-------------|----------|------------|
Step 3: Parse Arguments
--add <description>: Add a new issue. Ask for severity (high/medium/low) if not obvious from context. Auto-increment ID from highest existing ID + 1. Set source to "manual" and date to current timestamp.--resolve <id>: Move the issue from Open to Resolved. Ask for a brief resolution note.--list(default when no arguments): Display current issues.
Step 4: Execute Action
For --add:
Append a new row to the Open Issues table:
| {next_id} | {severity} | manual | {description} | {YYYY-MM-DD} |
Confirm:
"Issue #{id} added: {description}"
For --resolve:
- Find the issue by ID in the Open Issues table
- Remove it from Open Issues
- Add it to Resolved Issues with resolution timestamp and note
- Confirm:
"Issue #{id} resolved: {resolution_note}"
For --list (default):
Display issues grouped by severity:
Shipyard Issues
═══════════════
High Priority ({count})
#{id}: {description} [source: {source}, {date}]
Medium Priority ({count})
#{id}: {description} [source: {source}, {date}]
Low Priority ({count})
#{id}: {description} [source: {source}, {date}]
Total: {open_count} open, {resolved_count} resolved
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 · 111 lines · 8 tokens per session scan A d3ce3d1b2912
issues is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 659 once invoked, about $0.0000 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
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.