Works with the AI Agents you already use
Security Release Gate
Make the final AppSec go or no go decision without confusing missing evidence with failure
$15
Security Release Gate
Example session with this skill installed
Run the final security release gate for this synthetic release. The required controls are tenant authorization, session invalidation after password reset, and sensitive data logging. We have PASS evidence for tenant authorization and logging, but the session invalidation fix has no independent retest evidence yet. Produce the control classifications and final security release decision without treating missing evidence as a failed control.
- Read your context and instructions
- Compiled the security release gate
Security Release Gate Record
Release scope
Synthetic application release candidate.
Required controls
Tenant authorization
Session invalidation after password reset
Sensitive data logging
Control SRG-01
Security property
Cross tenant resource access must be prevented.
Evidence supplied
Independent negative authorization test covering Tenant A access to a Tenant B resource.
Evidence status
APPLICABLE
Control result
PASS
Reason
The supplied independent test demonstrates that the required tenant boundary is enforced for the release scope represented by the evidence.
Control SRG-02
Security property
Sessions that must be invalidated after password reset must no longer authorize protected operations.
Evidence supplied
Implementation record for the session invalidation fix.
No independent post fix verification was supplied.
Evidence status
INSUFFICIENT FOR FINAL VERIFICATION
Control result
BLOCKED
Reason
The implementation record shows that a change was made, but it does not independently prove that the required runtime security property now holds.
This is not classified as FAIL because the supplied evidence does not demonstrate that the control is broken.
Control SRG-03
Security property
Protected customer fields must not appear unredacted in application logs.
Evidence supplied
Focused security test using synthetic protected values.
Evidence status
APPLICABLE
Control result
PASS
Reason
The supplied test provides evidence for the required logging property within the stated scope.
Control Summary
Control
Result
Release impact
Tenant authorization
PASS
Satisfied
Session invalidation
BLOCKED
Required evidence missing
Sensitive logging
PASS
Satisfied
Gate Execution Result
COMPLETE
The release gate executed successfully and all required controls were classified.
Security Release Decision
BLOCKED
Decision Basis
The release cannot receive security sign off because required independent verification for session invalidation is missing.
No FAIL is recorded for that control because available evidence does not demonstrate control failure.
Required Next Evidence
Run the approved session lifecycle verification against the release candidate and provide the resulting PASS, FAIL, or INCONCLUSIVE evidence.
After that evidence is available, rerun this gate.
Authorization Boundary
A future PASS from this workflow would mean that the scoped AppSec evidence supports security release readiness.
It would not deploy the application, merge code, authorize production access, or replace the organization's release authority.
Connects securely to your tools. The creator never sees your data.
About this skill
Aggregates scoped security evidence into a final AppSec release assessment. It evaluates each required control against the evidence available, classifies the control as PASS, FAIL, or BLOCKED, and keeps the gate execution result separate from the actual release decision.
What it does
- Aggregates security requirements, test results, review findings, retest evidence, and unresolved security conditions.
- Evaluates each in scope control against explicit acceptance criteria.
- Classifies controls as PASS, FAIL, or BLOCKED.
- Treats missing or insufficient evidence as BLOCKED rather than inventing a failure.
- Separates gate execution status from the security release decision.
- Records the evidence supporting every control classification.
- Identifies unresolved findings and missing verification.
- Produces a final security release recommendation.
- Does not deploy, merge, publish, or authorize production changes.
How it works
- Release scope identifies the security controls and findings that must be evaluated.
- Evidence intake gathers the relevant requirements, security testing results, review records, retest evidence, and accepted exceptions.
- Evidence applicability checks whether each artifact actually supports the control being evaluated.
- Control classification assigns PASS, FAIL, or BLOCKED using the available evidence.
- Unresolved risk review records open findings, missing verification, and applicable exceptions.
- Gate execution records whether the assessment itself completed successfully.
- Release decision produces the final AppSec verdict separately from the execution status.
- Handoff identifies any evidence or remediation required before the gate can be rerun.
Control semantics
PASS
The required security property is supported by sufficient applicable evidence.
FAIL
Available evidence demonstrates that the required security property is not satisfied.
BLOCKED
The gate cannot establish PASS or FAIL because required evidence is missing, incomplete, stale, incompatible with the release scope, or otherwise insufficient.
Missing evidence is not automatically a failed control.
Boundaries
This is a read only security release assessment.
Creation of security requirements belongs to security-requirements.
Execution of security verification belongs to security-testing or the appropriate specialist retest workflow.
Implementation or remediation work must happen before this gate, using the appropriate remediation and implementation skills.
General engineering readiness belongs to ship-gate. security-release-gate answers the narrower question of whether the available AppSec evidence supports security release readiness.
The skill does not deploy an application, merge code, approve infrastructure changes, or convert a security PASS into deployment authorization.
Why this beats prompting it yourself
Generic release reviews often collapse evidence collection, security testing, risk acceptance, and release authorization into a single yes or no answer. They also tend to treat missing evidence as either an implicit PASS or an automatic FAIL. This skill keeps those concepts separate and produces an auditable security decision based only on evidence that actually applies to the release.
Validation
At pack level, JetFerrari Security Engineering passed 58/58 routing integrity checks with zero unresolved cases.
This skill is also covered by pack level structural, installation, discovery, and behavioral validation. No unsupported individual runtime qualification is claimed here.
Use cases
- Run the final AppSec gate before release.
- Aggregate security testing and retest evidence into one verdict.
- Distinguish failed controls from controls blocked by missing evidence.
- Check whether required security fixes have independent verification.
- Produce an auditable security release decision.
- Identify exactly what evidence is still required before security sign off.
Known limitations
The quality of the release decision depends on the completeness, freshness, applicability, and integrity of the supplied security evidence. The gate does not independently recreate every upstream security test or review. Missing evidence can result in BLOCKED controls and a blocked release decision. A security PASS is an AppSec assessment only and does not authorize deployment, merge, production access, or business release.
Part of JetFerrari Security Engineering.
The quality of the release decision depends on the completeness, freshness, applicability, and integrity of the supplied security evidence. The gate does not independently recreate every upstream security test or review. Missing or insufficient evidence can result in BLOCKED controls and a blocked release decision. A security PASS is an AppSec assessment only and does not authorize deployment, merge, production access, or business release.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
Access is limited to security requirements, test results, review records, remediation evidence, retest evidence, exceptions, and release context supplied for assessment. The skill may use local read only inspection commands. It does not modify project files, execute deployment actions, access production credentials, change release state, or authorize deployment.