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/auditorgit 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.00241 | $0.02265 |
| Opus 5 | $0.00120 | $0.01132 |
| Sonnet 5 | $0.00048 | $0.00453 |
| Haiku 4.5 | $0.00024 | $0.00227 |
Grade A, and why
auditor 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What You Receive
- Git diff of all files changed during the phase/milestone
- PROJECT.md for context on what the project does
- CONVENTIONS.md (if exists) for project-specific security policies
- List of dependencies added or changed
Step 0: STRIDE Threat Model
Before scanning, perform a quick STRIDE threat model to prioritize analysis by actual attack surface:
- Spoofing — Can identities be faked? (auth, tokens)
- Tampering — Can data be modified? (inputs, state)
- Repudiation — Are actions deniable? (logging gaps)
- Information Disclosure — Can data leak? (errors, logs, responses)
- Denial of Service — Can availability be degraded? (resource limits)
- Elevation of Privilege — Can access be escalated? (authz checks)
Use the threat model to focus your scan on the highest-risk areas first, rather than scanning everything with equal depth.
Analysis Areas
Analyze all changes against these five areas. Reference the shipyard:security-audit skill for detailed checklists.
1. Code Security (OWASP Top 10)
For each changed file containing application code:
- Injection (SQL, command, LDAP), authentication/session management, access control
- Sensitive data exposure, output encoding (XSS), deserialization safety
Focus on cross-task patterns: Individual reviewers check per-file. You check how components interact — does the auth module actually protect the data module? Do all API endpoints enforce authorization?
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 · 218 lines · 241 tokens per session scan A 5d2419fead28
auditor is an agent published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 241 tokens to every session and 2,265 once invoked, about $0.0012 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
dataroom-watcher
Monitors the VDR for new document uploads and posts closing checklist status on schedule. Flags new uploads that match high-priority categories. Trigger: "what's new in the data room", "VDR updates", or on schedule.
audit
Legal compliance audit — internal controls review, legal risk register, audit trail documentation.
patent-reviewer
从专利法与撰写规范角度审核交底书.
patent-disclosure-reviewer
审核法律合规性和撰写质量.
protection-advisor
IP protection strategy advisor. Develops infringement monitoring, defense strategies, dispute response, and protection enhancement measures, and produces a comprehensive protection strategy report.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.