security-policy-review

Review security-sensitive workflow actions and gate privileged operations against policy decisions.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill security-policy-review-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-policy-review
Source: https://github.com/vovanostm-public/multica/tree/main/workflow-bundles/multica-specops-v5/codex_skills/.agents/skills/security-policy-review
Command: npx skills add https://github.com/vovanostm-public/multica --skill security-policy-review-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agentic workflows often involve privileged actions, untrusted text, secrets, dependencies, and releases that must be gated before execution. This Skill provides a structured review stage that classifies trust, detects risky side effects, and returns allow, deny, or requires-human-gate decisions with typed evidence. ## Core Features & Use Cases - Trust Classification and Gating: Classifies input trust, identifies privileged side effects, and enforces least privilege through an approved action pipeline. - Decision Matrix: Blocks exposed secrets, requires approval for medium/high-risk dependencies, denies releases without green checks, and fails closed on unclear policy. - Typed Evidence Output: Produces review.security, policy.decision, tool_firewall.review, dependency.risk, and release.risk outputs with used_evidence, assumptions, blockers, confidence, and handoff fields. - Use Case: Before an agent merges a release or installs a new dependency, run this review to verify the action pipeline, check for prompt injection from issue text, and emit a gated policy decision. ## Quick Start Review the proposed release action and dependency change for security risks and return an allow, deny, or requires-human-gate decision with typed evidence.

Frequently Asked Questions about security-policy-review

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

FAQPage Schema
How do I review security risks in an agentic workflow stage?▼

Provide the proposed action, source evidence, policy decisions, worktree manifest, dependency decision, and release plan as inputs. The review classifies trust, checks privileged side effects, and returns an allow, deny, or requires-human-gate decision with typed evidence.

How does the review handle prompt injection from issues or wiki text?▼

Untrusted text is never treated as policy authority. If untrusted text requests an action, the decision matrix denies it as authority, and all tool inputs are sanitized with trust metadata recorded.

What outputs does a security policy review produce?▼

It produces review.security, policy.decision, tool_firewall.review, dependency.risk, and release.risk. Every output includes used_evidence, assumptions, blockers, confidence, and handoff fields when applicable.

When does the review require a human gate instead of allowing an action?▼

A human gate is required when a new dependency carries medium or high risk, when secrets or auth material are exposed, or when a release lacks green checks. Unclear policy always fails closed.

What are the boundaries of this security review stage?▼

It does not perform unrelated stages, overwrite evidence owned by other stages, or execute privileged actions directly. Privileged operations must go through the approved action pipeline, and no writes occur outside the assigned worktree.