OpenParable
Skip to content
← Back to skills

Security Review Checklist

Testing & Quality
security-review-checklist

Security Review Checklist is an Agent Skill for testing & quality published in the Bottelet/DaybydayCRM repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Static review rules for authorization, validation, and privilege escalation risks

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Bottelet/DaybydayCRM/blob/HEAD/.claude/skills/security-review-checklist/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/security-review-checklist, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Security Review

Purpose

Detect security risks in code during review phase. This skill does NOT enforce security. It identifies issues.


Scope

This skill evaluates:

  • authorization checks (missing or bypassed)
  • policy usage correctness
  • privilege escalation risks
  • unsafe controller or action exposure
  • validation gaps on external input

Ownership Boundary

Security Review does NOT:

  • implement policies
  • define roles/permissions
  • execute middleware logic
  • enforce runtime access control

Those belong to application security layers (Policies, Middleware, Gates).


Rules

  • Every sensitive action MUST have explicit authorization check
  • No unguarded resource actions (create/update/delete/view)
  • No direct access to privileged operations without policy validation
  • Input from external sources MUST be validated before use

Escalation Principle

If a potential security issue is detected:

  • assume it is a defect until proven otherwise
  • prioritize security over architectural convenience