Agent skill · Security

running-security-release-gate

Use when running security release gate is required during security work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.

casioreview20-glitch11★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add casioreview20-glitch/forge-os --skill running-security-release-gate --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Version: 0.2.0
Declared author: forgeos-community
Requires: ForgeOS-compatible Agent Skills hosts; no provider-specific model required.
Path: skills/core/security/running-security-release-gate/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 11
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Running Security Release Gate ## Overview This skill owns one bounded responsibility: **running security release gate**. Its focus is make a release decision from unresolved findings, required controls, test evidence, provenance, and explicit residual-risk ownership. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope. ## Trigger Activate only when the project is in one of these stages: `architecture`, `implementation`, `verification`, `release-readiness`, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request. ## Required Inputs - `verification-report` - `security-review` - Current gate result, open findings, artifact hashes, and invalidation state - Required tools: none - Optional tools: none - Confirmed human decisions relevant to this scope ## Method-Specific Protocol 1. Resolve the assurance profile and enumerate mandatory security evidence. 2. Verify every critical and high finding against closure evidence rather than status labels. 3. Check dependency, secret, authorization, tenant, prompt injec

What's inside
Steps it walks through
  1. Overview
  2. Trigger
  3. Required Inputs
  4. Method-Specific Protocol
  5. Procedure
  6. Verification Questions
  7. Evidence Packet
  8. Output Contract
  9. Quality Gate
  10. Forbidden Shortcuts
  11. Failure Modes
  12. Escalation and Invalidation
  13. Handoff
  14. Token and Context Policy
Ships with 1 file
  • contract.json
More from forge-os
All skills →
About this skill
What does the running-security-release-gate skill do?

Use when running security release gate is required during security work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.

How do I install it?

Run `npx skills add casioreview20-glitch/forge-os --skill running-security-release-gate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From casioreview20-glitch/forge-os, a repository with 11 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going