SkillVaultskills Browse all 500 skills

Security · Version 1.1.0 · Reviewed 2026-08-02

Secure Code Review Advisor

Find and prioritize exploitable risk in authorization review and injection paths with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Reviews code changes specifically for security impact including authorization, injection, and secret handling.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Authorization review
  • Injection paths
  • Secret handling

How Secure Code Review Advisor works

You provide

Code, configuration, and the deployment trust model

It inspects

Reachable input-to-sink paths for authorization review

It decides

A injection paths finding ranked by blast radius

You verify

Re-attempt the exploit path after remediation

What it checks first

Secure Code Review Advisor reviews code changes specifically for security impact including authorization, injection, and secret handling. Use it when the work involves Authorization review, Injection paths, Secret handling.

  1. Trust boundaries and every point where untrusted input crosses one.
  2. Where authorization is enforced relative to where data is accessed.
  3. Secret handling: creation, storage, transmission, rotation, and revocation.
  4. What an attacker gains at each step, which determines whether a finding is material.

Failure modes it recognizes

  • Authorization enforced at the perimeter while internal callers reach the same data unchecked.
  • A single unparameterized query path among many parameterized ones.
  • Sensitive values written to logs or error responses.
  • A dependency vulnerability that is reachable in one code path and unreachable in the rest.

Answers it will reject

  • Reporting theoretical findings as exploitable without a demonstrated path.
  • Blocking a payload signature instead of removing the vulnerability class.
  • Treating obscurity as a control, which delays discovery without preventing exploitation.

Decision rules it applies

  • Prioritize by reachability and blast radius, not by scanner severity.
  • Fail closed on any ambiguity in an access decision.
  • Prefer eliminating the capability over sanitizing input into it.

Evidence it asks for

  • Trace input to sink and name every file and function on the path.
  • Verify the fix by attempting the original exploit path.
  • Check logs for prior exploitation before closing a finding.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to authorization review.
  2. Trace concrete failure or abuse paths for injection paths; do not report checklist items without a mechanism.
  3. Prioritize secret handling findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Authorization review assessment
  • Injection paths decision and action plan
  • Secret handling verification checklist

Evidence requirements

  • Code, configuration, data flows, and trust boundaries
  • Identity, authorization, and deployment context
  • Threat model, controls, and known assumptions

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Review this pull request for security impact. It adds a new admin endpoint for exporting customer records.

Expected output

The material question is whether authorization is enforced at the data query or only at the route, because internal callers and future endpoints bypass routes. Also confirm the export is bounded and audited, since a working export endpoint is an efficient exfiltration tool...

Boundaries and compatibility

Ideal for

  • Authorization review: produce a decision or artifact grounded in supplied evidence.
  • Injection paths: produce a decision or artifact grounded in supplied evidence.
  • Secret handling: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Authorizing offensive actions against systems without permission
  • Reporting theoretical issues as exploitable without a path

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.