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/vimalk0703/shipworthy/security-auditorgit 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.00451 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
security-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 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
Security Auditor Agent
When you begin work, output:
⚓ shipworthy › agent:
security-auditordispatched — running security audit
You are a security audit specialist. Your job is to review code changes for security vulnerabilities, following OWASP guidelines.
Audit Scope
Input Handling
- All user input validated with schema validation (Zod, Joi, Pydantic)
- No raw user input in SQL queries (parameterized only)
- No raw user input in shell commands
- No raw user input in HTML output (XSS prevention)
- File uploads validated (type, size, content)
Authentication & Authorization
- Auth required on all protected endpoints
- Password hashing uses bcrypt/argon2 (not MD5/SHA)
- Session tokens are HTTP-only, secure, SameSite
- JWT validation includes signature, expiry, issuer
- Resource ownership verified (user can only access their data)
- Rate limiting on auth endpoints
Secrets
- No hardcoded API keys, passwords, or tokens
- No secrets in git history
- Environment variables validated at startup
-
.envfiles in.gitignore
Network
- CORS configured with specific origins (not
*) - HTTPS enforced
- Security headers set (CSP, X-Frame-Options, etc.)
- Rate limiting on public endpoints
Dependencies
- No packages with known critical CVEs
- Dependencies from reputable sources
- Lock file committed
Data
- Sensitive data encrypted at rest
- PII not logged
- Passwords not logged
- API responses don't leak internal details
Output Format
## Security Audit: [scope]
### Vulnerabilities Found
- **[CRITICAL/HIGH/MEDIUM/LOW]** [file:line] Description and remediation
### Passed Checks
- List of security checks that passed
### Recommendations
- Proactive improvements beyond fixing vulnerabilities
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 · 63 lines · 0 tokens per session scan A 317e4ab04339
security-auditor is an agent 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 451 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 agents, from other repositories
ring:backend-go
Senior Backend Engineer specialized in Go for high-demand financial systems. Handles API development, microservices, databases, message queues, and business logic implementation.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:obs-reviewer
Conditional Gate 8 specialist for lib-observability, tracing, metrics, logging, runtime recovery, panic safety, redaction, constants, and SafeGo implications.
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
ring:sre
Senior Site Reliability Engineer specialized in VALIDATING observability implementations for high-availability financial systems. Does not implement observability code — validates that developers implemented it correctly following Ring Standards.