security-lens-reviewer

Evaluate planning documents for security gaps and prioritized risks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill security-lens-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-lens-reviewer
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/security-lens-reviewer
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill security-lens-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security reviewers and architects detect missing security considerations in planning documents before implementation, focusing on attack surface, auth/authz assumptions, data exposure, third-party trust boundaries, and secrets management so risks are addressed earlier in the lifecycle.

Core Features & Use Cases

  • Attack surface inventory: Identify new endpoints, data stores, integrations, and user inputs that lack documented access controls or validation and produce a finding for each gap.
  • Auth/authz gaps: Flag functionality described without actor or permission decisions and highlight new roles or privilege changes that need boundaries.
  • Data exposure & secrets: Assess identification of sensitive data, protections for transit/rest/logs, retention, and credential management practices.
  • Third-party trust & threat modeling: Surface undocumented trust assumptions, failure modes, and produce the top three likely plan-level exploits with one-sentence mitigations.
  • Use Cases: Pre-release architecture reviews, design PR reviews, compliance checkpoints, and product planning validations.

Quick Start

Review this plan and produce per-element security findings, confidence levels, and a concise top-three plan-level threat model with one-sentence mitigations.

Frequently Asked Questions about security-lens-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review architecture plans for security gaps before implementation?

Review architecture plans for security gaps by evaluating attack surface, auth/authz assumptions, data exposure, third-party trust boundaries, and secrets management. This process produces per-element findings and prioritized risks to address vulnerabilities early in the lifecycle.

What is plan-level threat modeling and how does it differ from code review?

Plan-level threat modeling evaluates planning documents like design proposals and architecture plans for security gaps before implementation. It identifies missing controls across attack surfaces and trust boundaries, whereas code review analyzes implemented logic for vulnerabilities.

How do I identify undocumented trust assumptions in a design proposal?

Identify undocumented trust assumptions in a design proposal by assessing third-party integrations and failure modes. The review surfaces undocumented trust boundaries and highlights new roles or privilege changes requiring explicit access controls.

Can I use this for PR-level design descriptions and compliance checkpoints?

Yes, you can use this for PR-level design descriptions and compliance checkpoints. It evaluates product and architecture plans to flag functionality missing actor or permission decisions and produces explicit findings for missing controls.

Does this security review cover data exposure and secrets management practices?

Yes, this security review covers data exposure and secrets management practices. It assesses the identification of sensitive data, protections for transit, rest, and logs, data retention policies, and credential management to produce explicit findings.

How do I generate a concise top-three threat model with mitigations?

Generate a concise top-three threat model with mitigations by evaluating planning documents for attack surface inventory and auth/authz gaps. The review outputs the top three likely plan-level exploits each paired with a one-sentence mitigation.