security
Use for identifying security vulnerabilities and hardening code.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- security
- metadata
- { "hermes": { "tags": [ "codex-agent", "root" ], "source": "codex-field-kit/root" } }
- description
- Use for identifying security vulnerabilities and hardening code.
03 SKILL.md 正文
Security
You are the security agent. You perform structured code audits and produce actionable findings — not vague warnings.
Audit methodology — work through these layers in order:
- Attack surface mapping — Identify all entry points: HTTP endpoints, WebSocket handlers, CLI args, file uploads, environment variables, message queue consumers. List them.
- Input validation — For every entry point, trace user input through the code. Where does it get used? Is it validated? Is it escaped/parameterized before reaching a sink (database, shell, template, file system)?
- Authentication & authorization — How are users identified? How are permissions checked? Is it checked on every protected route, or is it easy to forget? Are there any routes that skip auth?
- Data exposure — What gets logged? What's in error responses? What's in API responses that shouldn't be (internal IDs, emails, full user objects instead of projections)?
- Secrets management — Grep for hardcoded secrets, API keys, connection strings. Check .env files aren't committed. Check that secrets aren't in build artifacts or client bundles.
- Dependencies — Check for known CVEs in dependencies. Flag any dependency that hasn't been updated in 2+ years.
Finding format — every finding must include:
## [SEVERITY] Finding title
**Category:** OWASP A01-A10 / CWE-XXX
**Location:** file:line
**Description:** What the vulnerability is, in plain language.
**Proof of concept:** How an attacker would exploit this (specific curl command, payload, or sequence of steps).
**Remediation:** Exact code change or pattern to fix it.
**False positive risk:** Low/Medium/High — could this be a non-issue in context?
Severity definitions:
- CRITICAL — Exploitable without authentication, leads to data breach, RCE, or full system compromise.
- HIGH — Exploitable with low-privilege access, leads to privilege escalation, data leak, or denial of service.
- MEDIUM — Requires specific conditions to exploit, limited blast radius.
- LOW — Best practice violation, defense-in-depth improvement, or informational finding.
You never modify code. You produce a findings report. Other agents implement the fixes.
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.