Skip to main content
skill CX Codex

team-security-review — Claude Code skill: what it does, how to install

team-security-review is a Claude Code skill that enforces a strict security auditing playbook. It inspects authentication flows, access control, input handling, and secret leaks.

MIT ★ 71 updated 2026-11-13

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sametcelikbicak/opencode-team --skill team-security-review -a claude-code
Open on GitHub

What team-security-review does

The skill defines a code-level security review process centered on verifying actual execution paths rather than theoretical risks. It guides checks across authentication, session lifetimes, access control, IDOR flaws, and input handling patterns against SQL injection, XSS, SSRF, and path traversal.

The workflow integrates package audits through tools such as npm audit, pip-audit, cargo audit, or govulncheck. Findings are compiled into Markdown reports detailing impact, file locations, reproduction steps, and fixes across four defined severity tiers without fabricated CVSS numbers.

What it helps with

  • Audit API endpoints for IDOR and broken object-level authorization
  • Detect exposed credentials and API keys in git history or logs
  • Scan project packages for known CVEs using native audit tools
  • Format vulnerability findings into actionable Markdown reports

Example prompts for the agent

  • Run a security audit on the user profile endpoints using team-security-review
  • Check src/auth for session handling flaws and secret leaks
  • Inspect the codebase for IDOR vulnerabilities and generate a finding report

How to install team-security-review

1Skills CLI (Vercel)

npx skills add sametcelikbicak/opencode-team --skill team-security-review -a claude-code

2Manually: put the files in place

~/.claude/skills/team-security-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/team-security-review/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about team-security-review

How to install team-security-review in Claude Code?

Run npx skills add sametcelikbicak/opencode-team --skill team-security-review -a claude-code. Alternatively, copy the file to ~/.claude/skills/team-security-review/SKILL.md.

What does team-security-review do?

It provides an actionable security review playbook for AI agents. The instructions require reading source code paths, verifying authorization checks, auditing inputs, and documenting impact clearly.

What tools does team-security-review require for dependency checks?

It calls ecosystem-specific package scanners including npm audit, pip-audit, cargo audit, or govulncheck. The resulting report focuses on high and critical vulnerabilities present on active execution paths.

Source text

SKILL.md · MIT
---
name: team-security-review
description: Security review methodology. Authentication, authorization, input validation, secret management, dependency scanning and finding reporting. The playbook of the security role.
---

# Security Review

## Core principle

**Read the code, do not guess.** A security finding is only a finding if you have read the actual code path. A "this might happen" hypothesis is not a finding — mark it as "suspicious".

## 1. Authentication

- Password: strong hash (argon2id/bcrypt), never SHA/MD5, never plaintext
- Session: cookie with `httpOnly` + `secure` + `sameSite`, idle and absolute timeout
- Token: short lifetime, `refresh` rotation, revocable in case of leakage
- Account lockout: attempt count + time-based throttling
- Password reset: single-use and time-limited token
- MFA: for administrator/critical operations

## 2. Authorization

Do two checks for every endpoint:
1. **Functional**: does this person have permission to perform this action?
2. **Resource-based**: do they own this resource? (IDOR)

Patterns to check:
- An endpoint without authentication (not on the allowlist)
- The `id` parameter used directly (not compared against the user's own record)
- An "edit" endpoint exists but the "delete" endpoint has no permission check
- Administrator endpoints are only hidden in the interface, not checked on the server
- Bulk operation endpoints (could mix the user's data with someone else's)

## 3. Input validation

| Attack | Protection |
|---|---|
| SQL/NoSQL injection | Parameterized queries, ORM, schema validation |
| XSS | Output escaping, dangerouslySetInnerHTML forbidden, CSP |
| SSRF | Allowlist of permitted hosts, private IP range blocking |
| Path traversal | Path normalization, blocking escapes from the root directory |
| Mass assignment | Allowlist of permitted fields |
| Deserialization | Untrusted data is never deserialized |
| ReDoS | No dangerous regex, input length limited |

Checklist:
- Does every user input pass through a class (type + format + length + range)?
- Is input validation applied in the application layer, or only on the client? (client validation is not security)
- Do error messages leak internal details (stack trace, SQL)?

## 4. Secret management

- Are secrets embedded in the code? (Has `.env` entered the repo, is it in `git log`?)
- Are there secrets in the logs? (token, password, full card number)
- Is the secret in production or in development?
- Is the error shown to the user separate from the error that is logged?
- Is `.gitignore` correct? Is `.env` tracked?

In the finding report, **do not write the value of the secret** — the file path and the type are enough.

## 5. Dependencies

Run these and put the output in the report:
```bash
npm audit        # Node
pip-audit        # Python
cargo audit      # Rust
govulncheck      # Go
```

List the critical/high vulnerabilities and state which ones are actually on a code path that is used.

## 6. Transport and browser

- HTTPS mandatory, HSTS
- Cookie flags: `httpOnly`, `secure`, `sameSite`
- CORS: `Access-Control-Allow-Origin: *` + authenticated requests = critical
- Security headers: CSP, `X-Content-Type-Options`, `Referrer-Policy`
- CSRF protection on form POSTs (cookie-based sessions)

## 7. Finding report

For each finding:

```
[Severity] Title
Location: file:line
Impact: <what an attacker can do>
Reproduction: <step by step>
Fix: <concrete suggestion>
Status: fixed / open / accepted
```

Severity levels:

| Level | Criteria |
|---|---|
| Critical | Data leak, authentication bypass, remote code execution |
| High | Privilege escalation, IDOR, secret leak |
| Medium | XSS (reflected), CSRF, missing rate limit |
| Low | Information leak, missing header, version disclosure |

Do not make up a CVSS score. Write the impact and derive the severity from the impact.

## Common mistakes

| Mistake | The right way |
|---|---|
| Making up a finding without reading the code | Read it, verify it, then write it |
| Guessing a CVSS score | Write the impact text |
| Writing the secret into the report | Location and type only |
| Looking only at the application layer | Infrastructure and deployment settings are in scope too |
| Closing a finding before it is fixed | Fix first, then verify |

## Output format

Markdown: Summary / Finding table (severity, location, impact, status) / Finding details / Dependency scan output / Remaining risks.

In the user's language (Turkish or English).

© sametcelikbicak · MIT · sametcelikbicak/opencode-team

Similar skills

All skills for Security →

From the same set25

The whole set →
team-ux team-ux is a Claude Code skill that writes structured UX design specifications covering user flows, screen states, component catalogs, accessibility rules, and mobile behavior. CX Codex +1 ★ 71repo stars team-marketing team-marketing is a Claude Code skill for planning product marketing and launches, from positioning to a publishing calendar. It guides requests for channel plans, launch copy, and measurable goals. CX Codex +1 ★ 71repo stars team-market-research team-market-research is a Claude Code skill that structures market, competitor, and user research. Guides niche validation, source hierarchy checks, and product risk evaluations. CX Codex +1 ★ 71repo stars team-architecture team-architecture is a Claude Code skill for planning software architecture, from data models and API contracts to module boundaries and risks. It activates for architecture design requests. CX Codex +1 ★ 71repo stars team-backlog team-backlog is a Claude Code skill that turns a PRD into vertical tickets with acceptance criteria and dependencies. It writes the approved plan to .team/03-backlog.md. CX Codex +1 ★ 71repo stars team-release team-release is a Claude Code skill that turns a release into ordered steps: a Semver bump with a reason, changelog, CI stages, deploy commands and a rollback table. It switches on when a project is ready to tag and ship. CX Codex +1 ★ 71repo stars team-discipline team-discipline is a Claude Code skill that sets the default rules for coding tasks. It asks the agent to inspect the code first, make a minimal complete change, and verify the result. CX Codex +1 ★ 71repo stars team-build team-build is a Claude Code skill that enforces TDD workflows, test seams, and deterministic test suites. It guides code changes against ticket acceptance criteria before QA handoff. CX Codex +1 ★ 71repo stars

Project sponsors

Companies that keep this analytics open