Common Exploit Verification Agent Skill
Enforce "No Exploit, No Report" policy with PoC construction standards, false-positive filtering, and evidence collection per vulnerability class across backend, frontend, and mobile. Use when validating security findings, constructing exploit proofs, filtering false positives, or writing pentest findings.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill common-exploit-verificationWhat comes with it
7 463 bytes besides the instructionThe instruction itself
8 sections, as written by the authorExploit Verification Standard
Priority: P0 (CRITICAL)
Always-Apply Rules
- No Exploit = No Report: Finding without reproducible PoC is discarded. No exceptions.
- No Theoretical Findings: "This could be exploited if..." → rejected. Demonstrate actual impact.
- No Tool Output as Evidence: Scanner output alone insufficient. Manual verification required.
PoC Construction
Every confirmed finding must include all fields:
ID: [unique identifier]
Vulnerability: [CWE-XXX: type name]
Platform: [backend|frontend|mobile-ios|mobile-android]
Component: [file:line or endpoint]
Severity: [Critical|High|Medium|Low] (CVSS: X.X)
OWASP: [mapping — e.g., A03:2021, API1:2023, M4:2024]
-- Proof of Concept --
Preconditions: [required state, auth level, config]
Steps:
1. [exact step with command/payload]
2. [expected vs actual result]
Payload: [exact input — copy-paste ready]
Evidence: [response body, status code, data returned]
-- Impact --
Impact: [what attacker gains — data, access, control]
Blast Radius: [lateral movement, escalation paths]
-- Remediation --
Fix: [specific code change, not generic advice]
Validation Gate
| Result | Action | Criteria |
|---|---|---|
| ✅ Confirmed | Include in report | PoC reproduces, impact demonstrated |
| ⚠️ Conditional | Include with conditions | Requires specific config/timing/race |
| ❌ Unconfirmed | Discard | Cannot reproduce despite 3 attempts |
| 🔄 Degraded | Downgrade severity | Partial impact, mitigating controls exist |
False Positive Filters
See false-positive-checklist for platform-specific filters.
Quick checks before reporting:
- SAST-only finding: Is the flagged code actually reachable from user input? Trace full data flow.
- Scanner noise: Does the "vulnerability" have compensating controls (WAF, middleware, framework defaults)?
- Version mismatch: Is the CVE for a function the project actually uses (reachability analysis)?
- Client-side only: Is the "bypass" only client-side while server enforces correctly?
Anti-Patterns
- No severity inflation: Missing header ≠ Critical. CVSS score must match demonstrated impact.
- No duplicate findings: Same root cause across endpoints = 1 finding with multiple affected components.
- No remediation without specificity: "Use parameterized queries" → include the exact code change for the affected file.
References
- False Positive Checklist — platform-specific false positive filters
- Exploit Playbook — PoC templates per vulnerability class (backend, frontend, mobile)
Other skills for the same job
different authors, same section of the catalogue
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms.
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
This skill should be used when the user asks to "escalate privileges on Linux", "find privesc vectors on Linux systems", "exploit sudo misconfigurations", "abuse SUID binaries", "exploit cron jobs for root access", "enumerate Linux systems for privilege escalation", or "gain root access from low-privilege shell". It provides comprehensive techniques for identifying and exploiting privilege escalation paths on Linux systems.
Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. Handles static/dynamic analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage, threat hunting, incident response, or security research.
This skill should be used when the user asks to "use Metasploit for penetration testing", "exploit vulnerabilities with msfconsole", "create payloads with msfvenom", "perform post-exploitation", "use auxiliary modules for scanning", or "develop custom exploits". It provides comprehensive guidance for leveraging the Metasploit Framework in security assessments.
Expert in secure mobile coding practices specializing in input validation, WebView security, and mobile-specific security patterns. Use PROACTIVELY for mobile security implementations or mobile security code reviews.
How to use it
Take hoangnguyen0403/common-exploit-verification from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.