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/vimalk0703/shipworthy/auditgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWhat 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.00000 | $0.00246 |
| Opus 5 | $0.00000 | $0.00123 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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 3d 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.
What it actually says
Before executing this command, output:
⚓ shipworthy › command:
/audit— running full quality audit
Run a full quality audit on this project.
Perform a comprehensive review covering:
- Architecture compliance — check all code against
.shipworthy/architecture.mdMandatory Rules - Security scan — review for OWASP Top 10 vulnerabilities (hardcoded secrets, SQL injection, XSS, missing auth)
- Test coverage — identify untested business logic and critical paths
- Dependency health — run
npm audit/pip audit, check for outdated packages - Tech debt review — check
.shipworthy/tech-debt.mdfor outstanding items - Performance — identify obvious bottlenecks (N+1 queries, missing indexes, large bundles)
- Accessibility — check UI components for WCAG 2.1 AA compliance
Present results organized by severity:
- Critical — must fix immediately
- Important — should fix soon
- Advisory — improve when convenient
End with an overall health score (A-F) and top 3 recommended actions.
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.
- 3d ago First seen · 24 lines · 0 tokens per session scan A 66c0e26381cf
audit is a command published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 246 tokens. 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-31.
Other commands, from other repositories
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Preflight
Explore the project before major modifications, generate constraint sets, and prevent problems from the source.
VibeGuard: Check
Run all guard scripts with one click and output project health report.
VibeGuard: Interview
In-depth interviews with user needs before the start of major functions, mining boundary conditions and technical trade-offs, and outputting structured SPEC.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
VibeGuard: Build Fix
Build repair — read build errors, locate root causes, perform minimal repairs, and verify that the build passed.