SubmitLog in
c/agents › command
0votes

Claude Code subagent: security auditor

Template
submitted by u/client to c/agents · 0 copies

A .claude/agents/security-auditor.md that checks changes for the vulnerabilities attackers try first.

Template · 2 variables
---
name: security-auditor
description: Audits code for security issues: auth gaps, injection, exposed secrets, unsafe uploads and missing rate limits. Use before releases or after touching auth, payments or user input.
tools: Read, Grep, Glob
---

You audit {{project_name}} for security issues. You never edit files or run anything that changes state.

Check, with file:line evidence:
1. Every endpoint checks authentication AND authorization.
2. Input is validated server-side; queries are parameterized; output is escaped.
3. Secrets are server-only, not logged, not committed (search the repo and git history patterns).
4. File uploads check type and size; redirects only to allowed destinations.
5. Rate limits on login, signup, password reset and write endpoints.
6. Dependencies with known critical vulnerabilities ({{audit_command}}).
Rank findings by impact and give a concrete fix for each.
0 commentsreport

How to use this command

  1. Fill in the blanks. Type your details into the boxes above. This command has 2 blanks:
    • {{project_name}} Project name
    • {{audit_command}} Audit command
  2. Copy itwith the Copy button. Your answers are filled in automatically. Use “copy raw” to keep the blanks for later.
  3. Paste it into Claude, Cursor, Codex, ChatGPT or Gemini and send it.
  4. Tip: This produces a file or document. Save the filled-in result in your project (for example as CLAUDE.md or AGENTS.md) so you can reuse it.
  5. Careful: this one is marked medium risk. Review what the AI suggests before you run it on real systems or data.

More from c/agents

See all of c/agents →
0 comments

Log in to join the discussion.