Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Security Fix Implementer

    1

    Implement the approved security fix without self certifying it

    $16

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Security Fix Implementer

    Security Fix Implementer

    Example session with this skill installed

    Implement the approved remediation for this synthetic invoice IDOR. The remediation record requires tenant scoped resource selection using the authenticated tenant context at the server side data access boundary. Make only the approved change, preserve existing same tenant behavior, run focused regression checks, and do not mark the fix as independently verified.

    • Read your context and instructions
    • Compiled the security fix implementer

    Illustrative synthetic demo. It demonstrates the expected implementation and handoff structure. No production repository, live tenant, or external system was modified.

    Security Fix Implementation Record

    Approved remediation

    Enforce tenant ownership during invoice resource selection using trusted authenticated tenant context.

    Implementation scope

    Synthetic invoice lookup service and its focused regression tests.

    Execution Gate

    Approved remediation record: PRESENT

    Causal control: DEFINED

    Enforcement boundary: DEFINED

    Authorized implementation scope: DEFINED

    Independent verification: REQUIRED AFTER IMPLEMENTATION

    Baseline

    The synthetic implementation selected an invoice using only the invoice identifier.

    The authenticated tenant context was already available to the service but was not included in resource selection.

    Implemented Change

    Resource selection was changed conceptually from:

    invoiceId
    

    to:

    invoiceId + authenticatedTenantId
    

    The tenant identifier comes from trusted authenticated context rather than client supplied request data.

    Scope Discipline

    No authentication flow was redesigned.

    No unrelated repository cleanup was performed.

    No identifier format was changed.

    No additional authorization architecture was introduced.

    The implementation remained limited to the approved causal control.

    Focused Regression Checks

    Same tenant invoice lookup

    PASS IN SYNTHETIC EXAMPLE

    The approved tenant may still retrieve its invoice.

    Nonexistent invoice

    PASS IN SYNTHETIC EXAMPLE

    Existing not found behavior remains intact.

    Cross tenant lookup

    EXPECTED TO BE DENIED BY THE IMPLEMENTED CONTROL

    This implementation result does not independently certify exploit closure.

    Files Changed

    Synthetic invoice data access module.

    Synthetic focused regression test.

    Original Security Evidence

    PRESERVED FOR RETEST

    The original cross tenant access condition should be reused by an independent verification workflow.

    Implementation Status

    IMPLEMENTED WITH FOCUSED REGRESSION PASS

    Security Verification Status

    NOT INDEPENDENTLY VERIFIED

    Handoff

    Route the implementation to independent security testing or exploit validation retest mode.

    The implementing workflow must not convert its own regression result into a final security verdict.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Implements an approved security remediation as the smallest bounded code or configuration change needed to remove the confirmed causal defect. It preserves the original security objective, runs focused regression checks, records what changed, and hands the result to independent verification instead of declaring its own fix secure.

    What it does

    • Requires an approved remediation record before implementation begins.
    • Uses the approved causal control and enforcement boundary as execution constraints.
    • Inspects the affected code or configuration before editing.
    • Implements the smallest change needed to satisfy the approved remediation.
    • Avoids unrelated refactoring and opportunistic cleanup.
    • Preserves relevant existing behavior and project invariants.
    • Runs focused regression checks after the change.
    • Records changed files, implemented controls, validation performed, and unresolved evidence gaps.
    • Preserves the original vulnerability evidence for comparison during independent verification.
    • Does not mark its own implementation as security verified.

    How it works

    1. Remediation gate confirms that an approved implementation ready security plan exists.
    2. Scope extraction identifies the authorized files, control, enforcement boundary, invariants, and verification requirements.
    3. Baseline inspection confirms the current implementation before edits are made.
    4. Bounded implementation applies the smallest approved code or configuration change.
    5. Focused regression checks verify that expected behavior still works and that the implementation is technically coherent.
    6. Change recording documents what was changed and which approved control it implements.
    7. Verification handoff preserves the original security objective and routes the result to an independent testing or retest workflow.

    Boundaries

    This skill implements an already approved security remediation.

    If the correct fix has not yet been designed, use security-remediation-planning first.

    If exploitability of the original finding remains uncertain, use exploit-validation before implementation.

    If the task is general vulnerability discovery or code review, use the corresponding specialist workflow.

    Successful implementation and regression checks do not prove that the vulnerability is closed. Independent verification belongs to security-testing, exploit-validation retest mode, or another appropriate verification workflow.

    Why this beats prompting it yourself

    Generic security fix prompts often combine diagnosis, remediation design, implementation, refactoring, and verification in one step. That makes scope drift difficult to detect and encourages the same agent that wrote the patch to declare it secure. This skill treats an approved remediation record as an execution contract, limits changes to the selected causal control, and separates implementation from independent verification.

    Validation

    This skill is part of the JetFerrari Security Engineering stack and is covered by pack level structural, routing, installation, discovery, and behavioral validation.

    No unsupported individual runtime qualification is claimed here.

    Use cases

    • Implement an approved authorization fix at the correct enforcement boundary.
    • Apply a bounded security patch without unrelated refactoring.
    • Implement an approved code or configuration remediation.
    • Preserve original exploit evidence for later retesting.
    • Run focused regression checks after a security change.
    • Produce a clean handoff for independent security verification.

    Known limitations

    This skill requires an approved remediation record with a sufficiently clear implementation boundary. It does not decide the remediation strategy from scratch, independently prove the original finding, or certify that its own implementation closes the vulnerability. Results also depend on the available source code, configuration, test environment, and regression capability. Independent verification remains required after implementation.

    Part of JetFerrari Security Engineering.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    This skill requires an approved remediation record with a sufficiently clear implementation boundary. It does not choose the remediation strategy from scratch, independently prove the original vulnerability, or certify that its own implementation closes the security issue. Results depend on the available source code, configuration, local validation environment, and regression capability. Independent verification remains required after 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 this skill and uses it on your task. It always asks before buying a skill.

    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

    Terminal / Shell
    Write Files
    Read Files

    Access is limited to the files and local validation commands required by the approved remediation record. The skill may read and modify bounded project code or configuration and run focused regression checks. It does not access production systems, retrieve credentials, expand the change beyond the approved security boundary, deploy changes, or mark its own implementation as independently verified.

    Listed24 days ago

    What's inside

    Frequently Asked Questions

    It implements an already approved security remediation as a bounded code or configuration change while preserving scope, regression requirements, original security evidence, and the separation between implementation and independent verification.

    Use it after Security Remediation Planning or another approved process has already defined the causal control, enforcement boundary, implementation constraints, and expected verification requirements.

    Security Remediation Planning determines what should change and where. Security Fix Implementer executes that approved decision. It should not redesign the remediation during implementation unless the approved plan is found to be impossible or materially incorrect.

    No. A focused regression result shows that the implementation behaves as expected within the tested scope. Final security closure requires an independent verification workflow that rechecks the original vulnerability condition.

    Provide an approved remediation record, the relevant project files, the permitted implementation boundary, and the local commands or test surface needed for focused regression. If the remediation decision is still unresolved, use Security Remediation Planning first.

    New in Security