Works with the AI Agents you already use
Security Remediation Planning
Plan the smallest security fix at the correct enforcement boundary before coding
$16
Security Remediation Planning
Example session with this skill installed
We confirmed an IDOR in the invoice endpoint. An authenticated user can request another tenant's invoice by changing the invoice ID because the handler loads the invoice by ID without enforcing tenant ownership. Plan the smallest causal remediation before any code is changed.
- Read your context and instructions
- Compiled the security remediation planning
Illustrative synthetic demo. It demonstrates the expected remediation planning structure. No production repository, live tenant, or external system was accessed or modified.
Security Remediation Record
Finding
Synthetic confirmed IDOR in an invoice retrieval endpoint.
Observed causal condition
The handler retrieves an invoice using only the supplied invoice identifier.
The authenticated principal has a tenant identifier, but the resource lookup does not enforce that the requested invoice belongs to that tenant.
Causal Path
- User authenticates successfully.
- Request supplies an invoice identifier.
- Handler queries the invoice by identifier alone.
- Resource is returned without a tenant ownership comparison.
- A valid user can therefore reach a resource outside the intended tenant boundary.
Root Cause
Tenant ownership is not part of the server side resource selection or authorization decision.
The defect is not the predictability of the invoice identifier itself. Changing identifier format would therefore not remove the causal authorization weakness.
Required Security Property
An authenticated principal may retrieve an invoice only when the invoice belongs to a tenant the principal is authorized to access.
Candidate Controls
Option A
Check tenant ownership after loading the invoice.
Assessment
Improves enforcement but allows an unauthorized object to be loaded before the authorization decision.
Option B
Scope the resource query by both invoice identifier and authorized tenant identifier.
Assessment
Places the ownership boundary directly in resource selection and prevents the unauthorized object from being returned by the normal lookup path.
Selected Remediation
Option B
Use the authenticated tenant context together with the invoice identifier when selecting the resource.
Implementation Boundary
Apply the control in the server side data access or service boundary responsible for retrieving tenant scoped invoices.
Do not rely on a client supplied tenant identifier as the authority source.
Variant Risk
Review other tenant scoped resource lookups that select objects by identifier without incorporating trusted tenant context.
This does not establish that those routes are vulnerable. It identifies the pattern that should be checked during implementation.
Regression Requirements
The approved implementation must preserve
- Access to invoices belonging to the authenticated tenant.
- Existing not found behavior for nonexistent resources.
- Existing privileged access paths where separately authorized by policy.
Verification Requirements
After implementation
- Confirm same tenant invoice access still succeeds.
- Confirm cross tenant invoice access is denied.
- Confirm the authorization decision uses trusted authenticated tenant context.
- Confirm equivalent invoice lookup paths enforce the same boundary.
Handoff
Status
READY FOR BOUNDED IMPLEMENTATION
The next workflow should implement only the approved causal control and preserve this remediation record for independent verification.
Connects securely to your tools. The creator never sees your data.
About this skill
Takes a confirmed security finding and turns it into an implementation ready remediation plan. It traces the causal path behind the vulnerability, identifies the correct enforcement boundary, selects the smallest control that removes the cause, and evaluates regression and variant risk before any code is changed.
What it does
- Starts from a confirmed vulnerability or sufficiently supported security finding.
- Reconstructs the causal path that allows the insecure behavior.
- Separates root cause from symptoms and downstream effects.
- Identifies the correct enforcement boundary for the fix.
- Compares candidate controls before selecting the smallest sufficient remediation.
- Evaluates regression risk, compatibility impact, and likely vulnerability variants.
- Defines implementation constraints and focused verification requirements.
- Produces an implementation ready remediation record.
- Remains read only and does not apply the fix itself.
How it works
- Finding intake records the confirmed behavior, affected surface, evidence, and impact.
- Causal analysis traces how the vulnerable state becomes reachable.
- Boundary selection identifies where enforcement must occur to eliminate the cause rather than mask the symptom.
- Control design compares plausible remediation options and selects the smallest sufficient control.
- Variant analysis checks whether equivalent paths could remain vulnerable after the proposed change.
- Regression planning identifies behavior that must remain intact.
- Verification planning defines the evidence required to demonstrate that the vulnerability is closed.
- Handoff produces a bounded remediation record for implementation.
Boundaries
This skill plans remediation. It does not implement or independently verify the fix.
If exploitability is still uncertain, route the finding to exploit-validation before remediation planning.
If the task is to discover vulnerabilities, use the appropriate review, assessment, or penetration testing workflow.
Implementation of an approved remediation belongs to security-fix-implementer. Independent verification after implementation belongs to security-testing or the appropriate retest workflow.
Why this beats prompting it yourself
Generic fix recommendations often jump directly from a symptom to a code change. That can move the vulnerability, protect only one path, or introduce unnecessary architectural changes. This skill first reconstructs the causal mechanism, then places the smallest sufficient control at the boundary where the unsafe behavior should actually be prevented.
Validation
At pack level, JetFerrari Security Engineering passed 58/58 routing integrity checks with zero unresolved cases. The complete security stack also passed installation and native discovery validation across the validated runtimes.
No unsupported individual runtime qualification is claimed here.
Use cases
- Plan the correct fix for a confirmed security vulnerability.
- Determine where an authorization control should actually be enforced.
- Convert a security finding into an implementation ready remediation record.
- Compare multiple possible security controls before changing code.
- Identify variant paths that could survive a superficial fix.
- Define focused regression and security verification requirements.
Known limitations
This workflow requires a confirmed or sufficiently supported security finding. If the causal mechanism or exploitability is still unresolved, additional review or validation may be required before a remediation plan can be considered implementation ready. The skill does not modify code, configuration, infrastructure, credentials, or production systems and does not certify that a later implementation is secure.
Part of JetFerrari Security Engineering.
This workflow requires a confirmed or sufficiently supported security finding. If exploitability, causal mechanism, affected boundary, or relevant implementation context remains unresolved, additional review or validation may be required before the remediation plan can be considered implementation ready. The skill does not modify code, configuration, infrastructure, credentials, or production systems and does not certify that a later implementation is secure.
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 the confirmed security finding, relevant source code or configuration, and project context needed to plan remediation. The skill may use local read only inspection commands but does not modify files, apply patches, change infrastructure, access credentials, contact production systems, or certify its own remediation as verified.