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/auditgit 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.00015 | $0.00730 |
| Opus 5 | $0.00008 | $0.00365 |
| Sonnet 5 | $0.00003 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
audit 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:audit - On-Demand Security Audit
You are executing an on-demand security audit. Follow these steps precisely.
Step 1: Parse Arguments
Extract from the command:
scope(optional): What to audit. Accepts:- No argument / "current": Audit uncommitted changes (
git diff+git diff --cached) - Diff range (e.g.,
main..HEAD): Audit commits in range - Directory path (e.g.,
src/): Audit all files in directory - "." or "all": Full codebase audit (changed files vs main branch)
- No argument / "current": Audit uncommitted changes (
If no scope and no uncommitted changes exist, default to full codebase audit against the main branch.
Step 2: Detect Context
- Check if
.shipyard/exists (optional — this command works anywhere). - If
.shipyard/config.jsonexists, readmodel_routing.security_auditfor model selection. - Otherwise, use default model: sonnet.
- Follow Worktree Protocol (see
docs/PROTOCOLS.md) — detect worktree context.
Step 3: Gather Scope
Based on the scope argument, collect the code to audit:
- Current:
git diff+git diff --cached - Range:
git diff <range> - Directory: List all files in directory for analysis
- Full codebase:
git diff main...HEADor all tracked files
Also gather:
- Dependency manifests (
package.json,requirements.txt,go.mod,Cargo.toml, etc.) - IaC files if present (
.tf,Dockerfile,docker-compose.yml, Ansible playbooks) - Configuration files (
.env.example, CI configs, etc.)
Step 4: Build Agent Context
Assemble context per Agent Context Protocol (see docs/PROTOCOLS.md):
- The diff/file content collected in Step 3
.shipyard/PROJECT.md(if exists)- Dependency manifest contents
- Working directory, current branch, and worktree status
Step 5: Dispatch Auditor
Dispatch an auditor agent (subagent_type: "shipyard:auditor") with:
- Follow Model Routing Protocol — resolve model from
model_routing.security_audit(default: sonnet) - max_turns: 15
- All context from Step 4
- Instruction: Perform comprehensive security analysis covering OWASP Top 10, secrets scanning, dependency audit, IaC security (if applicable), and configuration security
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 · 82 lines · 15 tokens per session scan A 93e830ae38d1
audit is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 730 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.