agentic-security-review

Read-only agentic-security and release-governance review skill for Codex and Claude Code.

1stIndeXR
by 1stIndeXR
Security · MIT · Updated: 3 months ago
0
stars
0
Forks
community
BBB
Safety
high
A
Quality

name: agentic-security-review description: Perform an explicitly requested, read-only agentic-security review, assessment of security-scanner evidence, source-review fallback, or security release gate. Specialize in AI agents, skills, plugins, MCP servers, tools, hooks, connectors, retrieval, memory, delegation, prompt injection, and release governance. Prefer configured scanners such as Codex Security, Semgrep, or CodeQL as evidence producers for routine repository or change scanning when available; use this skill to validate their evidence, cover agentic and policy gaps, and make a release-gate decision. Use a source-only review when the user explicitly requests it or suitable scanner evidence is unavailable, and label that limitation. Do not self-select for ordinary code review, run penetration tests or active exploitation, fix code, or start hosted scans without separate authorization.

Agentic Security Review

Apply a specialist agentic-security and release-governance review with explicit depth, a security map, and validated findings. Prefer verified scanner artifacts as evidence; do not duplicate a productized repository or change scan merely to recreate its coverage. This skill supports human security decisions. It is not penetration testing, dynamic analysis, or proof of exhaustive vulnerability coverage.

Establish the contract

Resolve and state:

This skill activates only on an explicit security-review request. An ordinary code, feature, or regression review — including one that touches authentication, authorization, or dependencies — belongs to a general code-review workflow (such as the deep-code-review skill), which reviews correctness first and may recommend this skill as a dedicated follow-up. When the user asks for both, run the general review and this review as separate passes and return both results.

Choose the operating route

Accept user-supplied or user-authorized hosted results as read-only evidence under security-review.md. Do not authenticate to a service, launch a scan, change scanner configuration, or retrieve private remote results unless the user separately requests that action and the environment grants the required authority.

Pin the review target

For a change subject, resolve and record the exact base and head revisions (SHAs when available) before reviewing. Verify the merge base rather than assuming a default branch. State whether staged, unstaged, and untracked files are included or excluded, and keep unrelated worktree changes out of scope. For a moving target such as an open pull or merge request, pin one revision pair, review that pair, and recheck the head revision at the end; if it moved, state that the findings apply to the reviewed revisions only. Attribute every change finding to the pinned diff. Bind scanner evidence to the same revision and scope before relying on it; otherwise record it as contextual evidence or a verification limitation.

Route references

Resolve paths relative to this SKILL.md:

Review discipline

Return one result

Lead with findings ordered by severity. Include the subject, pinned revisions, selected depth and route, accepted and rejected scanner evidence with reasons, security map summary for security-focused and release-gate reviews, atomic findings with severity, confidence, evidence, attacker path, impact, remediation direction, and standard citation with version when used; then questions, verification performed, limitations, and residual risks. State explicitly that absence of findings does not prove the subject secure.

A release-gate review must end with an explicit gate verdict: Pass, Block, or Incomplete — not approved. Pass requires positive evidence for the source and application-security assessment plus each release-gate area in security-review.md: organization- or repository-required scanner results, dependency scanning, secret scanning, CI/CD permission review, deployment and configuration hardening, artifact provenance, and rollback safety. Hosted and local scanner results are equally acceptable when their identity, target revision, scope, configuration, completion, coverage, and artifacts are verifiable. Codex Security, CodeQL, or a Semgrep Code run can support application-security evidence but does not by name prove dependency or secret scanning; require the applicable product, feature, or separate result for each area. Use Block only when available evidence demonstrates an unacceptable security risk or a violated release policy. When required evidence is unavailable, stale, misbound, incomplete, or could not be checked safely, return exactly Incomplete — not approved, not "Block," "Blocked pending evidence," or an equivalent; list the missing evidence, and do not substitute source review or an unrelated scanner result for it.

🔓 Sign in to unlock more
Sign in with GitHub