security-auditor

A code-review agent focused on finding security weaknesses in application changes using checks based on common web-security guidance.

In plain words
What is it for?
Use it to audit validation, database queries, shell commands, HTML output, uploads, passwords, sessions, tokens, ownership checks, rate limits, CORS, HTTPS, and security headers.
Why use it?
It helps expose unsafe handling of user input, weak authentication or authorization, leaked secrets, insecure file uploads, and risky network settings before release.

Agent

Part of the shipworthy plugin — 41 skills, 7 commands, 6 agents, 3 hooks shipped together

Install

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.

agentmods
npx agentmods add agents/vimalk0703/shipworthy/security-auditor
Clone the repo
git clone --depth 1 https://github.com/Vimalk0703/shipworthy

Or install shipworthy, the plugin that ships this one along with the rest of its 41 skills, 7 commands, 6 agents, 3 hooks.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 451 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 317e4ab04339, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

agents/security-auditor.md · 63 lines

What it actually says

Security Auditor Agent

When you begin work, output:

shipworthy › agent: security-auditor dispatched — 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
  • .env files 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
Changes

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.

  1. 3d ago First seen · 63 lines · 0 tokens per session scan A 317e4ab04339

Subscribe to this mod's changes

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.