BUNDLE Security scanned3 skills

    Security Controls & Release

    Security work becomes harder to govern when requirements, verification evidence, and release decisions are kept in separate places. Security Controls & Release brings three independent workflows into one commercial bundle for defining what must be true, checking what can be evidenced, and assessing release readiness without turning a PASS into deployment authorization.

    What this bundle gives you

    • Explicit security acceptance criteria for a defined scope.
    • Focused verification evidence against those criteria.
    • A bounded release-readiness assessment that keeps missing evidence visible.
    • Three independently usable workflows that can be selected according to the task.

    How the skills fit together

    The intended relationship is define -> prove -> gate. Security Requirements establishes reviewable security criteria. Security Testing produces evidence for a focused objective. Security Release Gate assesses the available evidence and surfaces what is still missing. The skills do not run automatically as one orchestrated process. Use the smallest workflow that matches the current question.

    Included Skills

    • Security Requirements: turns security concerns into explicit acceptance criteria and reviewable controls.
    • Security Testing: performs focused security verification and records evidence for a defined objective.
    • Security Release Gate: assesses release readiness from available evidence and makes missing evidence visible.

    Typical Workflows

    • For a new feature, define security requirements, produce focused testing evidence, then run a bounded gate assessment.
    • For an existing release, use the gate to identify missing evidence, then return to requirements or testing where the gap is located.
    • When a design question needs structured threat analysis, Threat Modeling is a separate Free entry product that can sit upstream of this workflow.

    Who It Is For

    Application security leads, engineering leads, and product teams that need a clearer handoff from security expectations to evidence and release review.

    Why Buy the Bundle

    The value is the separation of three decisions that are often blurred together: what must be true, what can be shown, and what the current evidence supports. The bundle keeps those roles distinct while making the related workflows available together for selective use.

    Boundaries

    A Security Release Gate PASS is not deployment authorization. Missing or insufficient evidence remains visible and may result in a blocked assessment. The bundle does not guarantee that controls are sufficient, that a vulnerability will be found, or that a release is safe. It does not provide automatic orchestration, and actual capabilities depend on the host, scope, permissions, and evidence available for the task.

    Individual Ownership

    This Agensi bundle contains three separate listings. Each included skill remains independently usable, independently owned, and selectable for work that does not require the other skills.

    Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.

    Jet Ferrari
    Created by
    Jet Ferrari
    $42$49
    Save 14% · $7

    One payment, lifetime access. 3 skills unlock instantly in your library.

    Money-back guarantee

    Instant unlock in your library

    Free updates from the creator

    What's included

    3 skills

    See it in action

    Security Requirements

    Security Requirements

    Example session with this skill installed

    Using this synthetic threat model, create testable security requirements for a multi tenant application. The identified risks are cross tenant resource access, weak session invalidation after password reset, and sensitive data appearing in application logs. Map applicable requirements to OWASP ASVS 5.0.0, define explicit PASS and FAIL criteria, and preserve traceability to each threat.

    • Read your context and instructions
    • Compiled the security requirements

    Illustrative synthetic demo. It demonstrates the expected requirements structure. No production system, live application, external account, or runtime environment was accessed.

    Security Requirements Record

    Scope

    Synthetic multi tenant application.

    Input risks

    • Cross tenant resource access
    • Session remaining valid after password reset
    • Sensitive customer information entering application logs

    Requirement SR-01

    Security property

    Tenant scoped resources must only be accessible to principals authorized for the owning tenant.

    Originating risk

    Cross tenant resource access

    Requirement

    Server side resource authorization must verify tenant ownership using trusted authenticated tenant context before a tenant scoped resource is returned or modified.

    PASS

    A request using a valid principal from Tenant A cannot read or modify a Tenant B resource through identifier substitution or equivalent direct resource access.

    FAIL

    A valid principal can obtain or modify a resource belonging to another tenant without an explicitly authorized cross tenant capability.

    Evidence expected

    A negative authorization test using separate tenant identities and known resources.

    Framework mapping

    Applicable OWASP ASVS 5.0.0 access control requirement or requirements should be recorded during implementation using the exact project approved ASVS reference.

    Traceability

    Threat T-01: Cross tenant resource access

    Requirement SR-02

    Security property

    A security sensitive credential reset must invalidate sessions that should no longer remain trusted.

    Originating risk

    Weak session invalidation after password reset

    Requirement

    After a successful password reset, previously issued sessions that are not explicitly intended to survive the reset must no longer authorize protected actions.

    PASS

    A session issued before the reset is rejected when reused after the reset according to the documented session policy.

    FAIL

    A pre reset session continues to authorize protected actions despite the policy requiring invalidation.

    Evidence expected

    A focused session lifecycle test covering session issuance, password reset, and reuse of the prior session.

    Traceability

    Threat T-02: Session persistence after credential reset

    Requirement SR-03

    Security property

    Sensitive customer data must not be emitted to application logs unless explicitly required and protected by an approved logging policy.

    Originating risk

    Sensitive data exposure through logging

    Requirement

    Application logging must exclude or redact protected customer fields before structured objects, errors, or request context reach logging sinks.

    PASS

    Representative application flows produce logs without the protected fields defined by the project data classification.

    FAIL

    A protected field appears unredacted in application logs during an in scope workflow.

    Evidence expected

    Focused log inspection using synthetic protected values.

    Traceability

    Threat T-03: Sensitive data in application logs

    Requirement Coverage

    ThreatRequirementVerification status
    T-01 Cross tenant accessSR-01NOT YET TESTED
    T-02 Session persistenceSR-02NOT YET TESTED
    T-03 Sensitive loggingSR-03NOT YET TESTED

    Evidence Boundary

    These are security requirements and acceptance criteria.

    No application control was executed.

    No security test was performed.

    No PASS result is claimed for the system itself.

    Framework mappings must be confirmed against the exact ASVS 5.0.0 control text used by the project before being treated as formal compliance traceability.

    Handoff

    Route SR-01 through SR-03 to security-testing after implementation evidence is available.

    The testing workflow should return PASS, FAIL, or INCONCLUSIVE evidence for each requirement without changing the requirements retrospectively to match the implementation.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads these skills and uses them on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every skill in this bundle goes through our trust checks.

    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.

    Frequently asked questions

    Yes — every skill in Security Controls & Release is also sold on its own product page. The bundle just packages them together at a discount (save 14% vs buying each one separately).

    Yes. When you own the bundle your connected agent can load the latest version of any included skill. Updates the creator publishes after your purchase are included at no extra cost.

    All skills in this bundle use the open SKILL.md standard and work with Claude Code, Cursor, Codex CLI, Gemini CLI, GitHub Copilot, Windsurf. The compatibility list on this page is computed from the included skills.

    The bundle price is set 14% below the combined retail price of the 3 paid skills included. You pay once and unlock every skill in your library instantly.

    Bundles are covered by the same money-back guarantee as individual skills. Doesn't do what its page promises? You get your money back.

    Start with Security Requirements when the security criteria are unclear, Security Testing when criteria exist but evidence is missing, and Security Release Gate when you have evidence to assess. You do not need to use all three for every task.

    No. It is a bounded assessment of the evidence available for the release. Deployment authority remains with the project owners and the applicable release process.

    No. Use the smallest workflow that matches the question. A requirements task, an evidence task, and a release assessment can be handled separately.

    Threat Modeling is a separate Free acquisition product. It can be considered upstream when a design question needs structured threat analysis, but it is not included in this paid bundle.

    More bundles from Jet Ferrari