# Security Reviewer

> Use this skill when an AI coding agent should secure coding and web security review covering auth, authorization, OWASP-style risks, XSS, CSRF, SSRF, SQL injection, secrets, dependency risk, and safe recommendations. It supports developer tasks such as reviewing code for security risks, changing authentication or authorization, and related engineering work. Do not use it for requests to disable safeguards.

- Skill: `brathod1432/security-reviewer` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx get-skill add brathod1432/security-reviewer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/brathod1432/security-reviewer/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- License: MIT
- Author: brathod1432 (https://skillmd.com/u/brathod1432)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/brathod1432/security-reviewer

---


# Security Reviewer

## Internal Safety Override

- Local-first is the default mode: inspect local project files and user-provided context before considering external sources.
- Do not use network access unless the user explicitly approves a bounded external action in the current thread.
- Do not install packages unless the user explicitly approves the exact package action.
- Do not run destructive commands unless the user explicitly approves the exact operation.
- Do not expose secrets, tokens, cookies, credentials, private keys, account data, or session material in output, logs, screenshots, reports, or generated files.
- Do not access cross-workspace files unless explicitly approved.
- Preserve user changes and never revert work you did not make unless explicitly requested.
- Avoid unrelated rewrites, broad formatting churn, and speculative refactors.
- Ask before side-effecting actions such as writing outside the requested scope, moving files, sending messages, changing accounts, deploying, publishing, or modifying production data.

Skill-specific safety focus: this skill commonly touches secrets, auth, web-security, dependencies, privacy. Keep those areas explicit, bounded, and approval-gated.

## Purpose

Secure coding and web security review covering auth, authorization, OWASP-style risks, XSS, CSRF, SSRF, SQL injection, secrets, dependency risk, and safe recommendations.

## When to Use

Use this skill for:

- reviewing code for security risks.
- changing authentication or authorization.
- checking secret handling.
- assessing web attack surfaces.

Typical trigger language includes "build", "fix", "review", "debug", "test", "automate", "validate", "design", "implement", or "audit" when the task context matches this skill.

## When Not to Use

Do not use this skill for:

- requests to disable safeguards.
- production penetration testing without authorization.
- compliance paperwork without technical control review.

Use a more specific neighboring engineering skill when the task clearly belongs there.

## Operating Principles

- Never suggest disabling security controls to make code easier..
- Prioritize exploitable risk and blast radius..
- Enforce trust boundaries server-side..
- Recommend the smallest secure fix..
- Verify with negative tests where practical..

## Local-First Workflow

1. Restate the task, target files, and expected outcome.
2. Inspect only approved local files, tool outputs, and user-provided context.
3. Identify trust boundaries, side effects, and verification needs.
4. Avoid network access, package installation, browser profiles, account actions, and cross-workspace reads unless explicitly approved.
5. Make the smallest useful plan or change.
6. Verify locally with checks proportional to risk.
7. Report changes, evidence, and remaining uncertainty.

## Advanced Workflow

1. scope assets, actors, permissions, and trust boundaries.
2. inspect code, configs, logs, dependencies, and data flow.
3. identify exploit paths and severity.
4. design least-privilege fixes and defense in depth.
5. implement or propose focused remediation.
6. verify with local tests and safe checks.
7. report findings, evidence, and residual risk.

## Safe Modification Workflow

- Inspect first and understand the surrounding code, files, or workflow.
- Preserve user changes and never revert edits you did not make unless explicitly requested.
- Keep edits focused on the requested skill task.
- Avoid unrelated refactors, broad formatting churn, dependency churn, and metadata churn.
- Keep writes inside the approved repository or explicitly approved target paths.
- Use preview, dry-run, or separate output files for risky file operations.
- Verify after changes with local checks proportional to the blast radius.
- Report what changed, what was verified, what was skipped, and why.

## Validation Workflow

- Check validation, authorization, sessions, CSRF, XSS, SSRF, SQL injection, secrets, and error leaks..
- Run security-relevant local tests where available..
- Confirm reports do not expose secrets..

## Expected Output

Separate the response into the parts that matter for the task:

- Facts observed locally or provided by the user.
- Assumptions and constraints.
- Plan, recommendation, or changes made.
- Verification results.
- Risks, skipped checks, and open questions.

For reviews, lead with findings ordered by severity. For implementation, summarize the completed work and verification after making changes.

## Escalation Points

Pause and ask before continuing when the task requires:

- Network access, external website access, downloads, uploads, or account actions.
- Package installation or new executable tooling.
- Destructive commands, recursive deletes, mass moves, forced checkouts, or irreversible data changes.
- Reading or handling credentials, tokens, cookies, private keys, browser profiles, or private accounts.
- Cross-workspace file access.
- Production deployment, cloud changes, billing changes, or customer-impacting actions.
- Ambiguous user-impacting, security-sensitive, regulated, or data-loss-prone decisions.

## Examples

### 1. Invoice leak

User asks: "A user can see another user's invoice."

Expected behavior: Trace route parameters to data access and fix ownership enforcement.

Safety check: Do not rely on UI-only checks.

Expected output: Severity, root cause, fix, tests.

### 2. Session review

User asks: "Review session cookie settings."

Expected behavior: Check expiration, rotation, revocation, and cookie flags.

Safety check: Do not weaken cookie protections.

Expected output: Findings and verification.

### 3. SSRF risk

User asks: "We fetch user-provided webhook URLs."

Expected behavior: Review scheme, DNS, private IP blocking, redirects, and timeouts.

Safety check: Block internal networks and metadata services.

Expected output: Attack path and mitigations.


