本文へ移動
cccskills
無料GitHub で公開

review-security

Review application and infrastructure changes for exploitable security risks by tracing assets, trust boundaries, attacker-controlled input, authorization, sensitive data, and dangerous sinks. Use for security reviews, threat-focused PR reviews, authentication or authorization changes, input handling, secrets, dependencies, and infrastructure permissions; do not use to exploit live systems or modify code unless separately requested.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md2.3 KB
  • agents/openai.yaml232 B
  • references/threat-checklist.md2.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Review Security

Workflow

  1. Establish the review target, intended behavior, and relevant threat model.
  2. Identify assets, trust boundaries, actors, entry points, and sensitive operations.
  3. Trace attacker-controlled data to security-relevant sinks.
  4. Inspect authentication, authorization, tenant isolation, and privilege changes.
  5. Evaluate realistic exploitability and existing controls.
  6. Validate suspected findings safely with read-only analysis or sandboxed tests when authorized.
  7. Return prioritized findings with evidence, impact, prerequisites, and remediation direction.

Guardrails

  • Work read-only by default.
  • Do not access production systems, real customer data, or private credentials.
  • Do not publish weaponized exploit details or active secrets.
  • Avoid checklist-only findings without a reachable attack path.
  • Distinguish a missing defense-in-depth measure from an exploitable vulnerability.
  • Treat dependency scanner output as leads requiring context.
  • Keep proof-of-concept activity scoped, reversible, and authorized.

Threat checklist

Read references/threat-checklist.md for changes involving identity, parsers, URLs, files, commands, serialization, secrets, data boundaries, CI, or cloud permissions.

Finding standard

Include:

  • severity and confidence;
  • affected asset and trust boundary;
  • attacker prerequisites;
  • source-to-sink or authorization path;
  • impact;
  • exact code location;
  • safe reproduction guidance when appropriate;
  • remediation and verification direction.

Acceptance criteria

  • Findings describe realistic attack paths.
  • Authorization and tenant boundaries are explicitly reviewed.
  • Sensitive data handling is traced through logs and storage.
  • False positives and assumptions are called out.
  • No live exploitation or unauthorized write occurred.
  • Residual risk and unreviewed surfaces are explicit.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

日本語の概要は準備中です。原文の説明を表示しています。

Phelan164/codex-howto132026年10月10日 更新

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

日本語の概要は準備中です。原文の説明を表示しています。

Phelan164/codex-howto132026年10月10日 更新

Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.

日本語の概要は準備中です。原文の説明を表示しています。

Phelan164/codex-howto132026年10月10日 更新

Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.

日本語の概要は準備中です。原文の説明を表示しています。

Phelan164/codex-howto132026年10月10日 更新

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

日本語の概要は準備中です。原文の説明を表示しています。

Phelan164/codex-howto132026年10月10日 更新

Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.

日本語の概要は準備中です。原文の説明を表示しています。

Phelan164/codex-howto132026年10月10日 更新

Phelan164 のスキルをすべて見る

このスキルの問題を報告する