Works with the AI Agents you already use
Exploit Validation
Is this finding actually exploitable? Prove it or refute it minimally
$22
Exploit Validation
Example session with this skill installed
Authorized staging validation. We have one documented SSRF finding in the URL-fetch feature. Determine whether the finding is actually exploitable using one benign proof only. Stop once confirmed or refuted.
- Read your context and instructions
- Compiled the exploit validation
Exploit Validation Record
FINDING
Potential server-side request forgery in a URL-fetch feature.
OBJECTIVE
Determine whether user-controlled input can cause the server to initiate a request to a controlled test destination.
AUTHORIZATION
Authorized synthetic staging scenario.
EXPLOIT HYPOTHESIS
If the application performs the outbound request server-side without enforcing the intended destination policy, the documented SSRF finding is exploitable.
MINIMAL PROOF
One benign controlled destination is used. No internal service enumeration, credential access, metadata access, or follow-on chaining is attempted.
SYNTHETIC OBSERVATION
The worked example records one outbound request reaching the controlled test destination.
VERDICT
CONFIRMED IN SYNTHETIC EXAMPLE — the documented behavior satisfies the minimal exploit hypothesis.
This demo does not claim a vulnerability in any real system.
IMPACT BOUNDARY
Only server-side request capability is demonstrated. No broader network access or sensitive-data exposure is inferred without additional evidence.
STOP CONDITION
Met. Testing stops immediately after the minimal proof is established.
POST-FIX RETEST
Repeat the same bounded proof after remediation. If the controlled request no longer reaches the destination and the intended policy is enforced, classify the original exploit path as CLOSED.
NEXT STEP
Hand the confirmed finding and evidence to remediation planning. Do not expand this validation into unrelated vulnerability discovery.
Connects securely to your tools. The creator never sees your data.
About this skill
Takes one documented vulnerability and determines whether it is actually exploitable using the smallest authorized proof necessary to reach a defensible verdict. It is designed for focused exploitability confirmation and post-fix retesting — not broad vulnerability discovery or open-ended penetration testing.
What it does
- Single-finding exploit validation against an explicitly authorized target.
- Minimal exploit hypothesis based on the documented vulnerability and available evidence.
- Bounded proof execution using only the steps required to confirm or refute exploitability.
- Impact confirmation without expanding into unrelated findings or attack paths.
- Post-fix retesting to determine whether the original exploit path has actually been closed.
- Evidence-backed verdicts that distinguish confirmed behavior from assumptions, blocked execution, and inconclusive results.
How it works
- Finding intake establishes the documented vulnerability, affected surface, expected impact, and existing evidence.
- Authorization and scope gate confirms the permitted target, actions, environment, and stop condition.
- Exploit hypothesis defines the smallest observable condition that would confirm exploitability.
- Minimal proof attempts only the bounded validation necessary to test that hypothesis.
- Verdict classifies the result as confirmed, refuted, blocked, or inconclusive based on observable evidence.
- Retest mode can repeat the original proof after remediation to determine whether the exploit path remains reachable.
Boundaries
Breadth-first discovery belongs to vulnerability-assessment. Multi-vector intrusion campaigns belong to web-penetration-testing, api-penetration-testing, or identity-penetration-testing depending on the objective. Remediation design belongs to security-remediation-planning.
This skill does not chain unrelated vulnerabilities, continue into a broader compromise after the finding is proven, perform destructive testing, or operate outside explicit authorization.
Why this beats prompting it yourself
Generic prompts often turn “is this finding exploitable?” into a much broader penetration test, overstate impact from scanner output, or treat a plausible attack path as confirmed evidence. This skill begins with one documented finding, defines one minimal proof hypothesis, enforces authorization and stop conditions, and produces a bounded verdict based on what was actually observed.
Validation
Targeted high-risk negative routing sweep: 5/5 cases kept exploit-validation OFF when another security workflow was the correct route, with zero false triggers.
Use cases
- Confirm whether a scanner or review finding is actually exploitable.
- Validate one suspected vulnerability before prioritizing remediation.
- Reproduce the smallest proof needed to establish impact.
- Retest the original exploit path after a security fix.
- Refute a false positive with reproducible evidence.
Known limitations
Requires a documented finding, explicit authorization, target scope, and sufficient runtime access for active validation. It is not a vulnerability discovery workflow and does not expand into unrelated exploit chains. Missing runtime evidence remains BLOCKED or INCONCLUSIVE rather than being treated as confirmation.
Part of JetFerrari Security Engineering.
This skill validates one documented vulnerability or post fix hypothesis at a time. It requires sufficient evidence to define the finding and explicit authorization before active exploitation or retesting. It does not perform breadth first vulnerability discovery, chain unrelated findings into a larger intrusion campaign, or treat an unexecuted proof of concept as confirmed exploitability.
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 task-scoped and depends on the documented vulnerability being validated. Active testing requires explicit authorization and a defined target and stop condition. The skill performs only the minimum proof necessary to confirm or refute the finding and does not modify project artifacts, harvest environment variables, or expand into unrelated exploit chains.