security-review

Reviews generated-project edits for path containment, secret exposure, and isolation violations.

6|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/josoroma/AppLoop --skill security-review-josoroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/josoroma/AppLoop/tree/main/.hermes/skills/security-review
Command: npx skills add https://github.com/josoroma/AppLoop --skill security-review-josoroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code edits can escape workspace boundaries, leak secrets, or run dangerous commands. This Skill provides a reusable security checklist to audit proposed file operations, shell commands, and preview iframe communication before they are approved. ## Core Features & Use Cases - Path Containment Auditing: Verifies every file read, write, and command target stays under the active project workspacePath after normalization and realpath resolution. - Secret and Command Guardrails: Blocks exposure of Hermes API keys, forbids NEXT_PUBLIC_HERMES_* variables, and rejects destructive or privilege-escalating commands. - Isolation and Iframe Checks: Distrusts browser-provided ports, process IDs, and session IDs, and requires preview communication to use approved channels with project id and nonce verification. - Use Case: Before completing a run that modifies a generated Next.js app, run this review to confirm no edit touches AppLoop source files, templates, or sibling project workspaces, and receive an approved, blocked, or needs-context decision. ## Quick Start Review the proposed changes for the current generated project and report any security violations with safe corrections.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I review AI-generated code changes for security issues?▼

Run a security review checklist against each proposed operation before completion. Verify path containment, secret exposure, dangerous commands, runtime isolation, and iframe boundaries, then mark each operation approved or blocked with a safe correction.

How to prevent AI agents from modifying files outside the project workspace?▼

Enforce path containment by normalizing and resolving the realpath of every file read, write, and command target, then confirming it stays under the active project workspacePath. Reject any operation targeting source files, templates, or sibling workspaces.

Can generated Next.js apps safely use environment variables for API keys?▼

Server-side environment variables are acceptable, but secrets must never reach browser code. Variables prefixed with NEXT_PUBLIC_ are bundled into client JavaScript, so NEXT_PUBLIC_HERMES_* keys are forbidden and must be blocked during review.

What commands should be blocked in AI-generated project edits?▼

Block destructive, global, privilege-escalating, or cross-project commands. Use an allowlisted environment so only vetted commands execute, and never trust browser-provided ports, process IDs, paths, or session IDs.

When does a security review return needs-context instead of approved?▼

A review returns needs-context when server-side project information is missing, such as the active workspacePath or project authorization state, making it impossible to verify containment or access. Gather the missing context before deciding.