dupcheck
$
npx mdskill add H-mmer/pentest-agents/dupcheckCheck for duplicate reports: $ARGUMENTS
SKILL.md
.github/skills/dupcheckView on GitHub ↗
--- name: dupcheck description: "Check if a vulnerability has already been reported. Searches platform hacktivity + local findings. Usage: /dupcheck <vuln_type> e.g. /dupcheck XSS in search endpoint" disable-model-invocation: false --- Check for duplicate reports: $ARGUMENTS 1. Determine the platform and program from `scope.yaml` in the current directory. 2. Use `bounty-platforms` MCP tool `search_hacktivity` with platform, program, and "$ARGUMENTS" as the query. 3. Also search local findings: `uv run python3 $CLAUDE_PROJECT_DIR/tools/dedup_findings.py --stats --db findings.json` 4. Read `hacktivity.md` if it exists and grep for related terms. 5. Report: - Exact or near matches from hacktivity (potential duplicates) - Related reports that might overlap - If the area appears heavily reported (high duplicate risk) - Verdict: likely unique, possible duplicate, or high duplicate risk ## Writeup Cross-Reference (if writeup-search MCP is available) After checking local findings, also search the writeup database: - Use `search_writeups` MCP tool with "<finding description> <target>" - If similar writeups exist, assess whether your finding is novel or a known pattern - Mention relevant prior art in the "Known Techniques" section of the report ## Top-Tier Duplicate Analysis Duplicate risk is about overlap of exploit primitive and affected asset, not keyword similarity. Report four verdict fields: - `same_asset_same_primitive`: likely duplicate unless your impact is strictly stronger - `same_primitive_different_asset`: possible duplicate; explain scope difference and novelty - `same_asset_different_primitive`: usually unique; prove a different root cause - `known_class_new_chain`: often worth reporting if the chain reaches a new impact tier Check disclosed writeups for patch language and response tone. If triagers historically close this class as N/A, require chain proof before submission. If public reports stop at a weaker impact, frame your report around the new capability, not the shared first step.
More from H-mmer/pentest-agents
- analyzeAnalyze recon output with AI to suggest high-value targets and attack strategies. Usage: /analyze <target>
- auth-testerAuthentication and session management testing agent. Use for login bypass, session fixation, password reset flow abuse, MFA bypass, OAuth flaws, and privilege escalation testing. Provide the application URL and any credentials for testing.
- autopilotAutonomous hunt orchestrator. INSATIABLE in --autonomous mode: enforces an EXHAUSTION CONTRACT (26 canonical hunter classes, surface probe A-I, depth-engine ≥25 attempts/class, wall-clock floor 90 min/target, PRE-COMPLETION GATE before any summary). No early stops, no clarifying questions, no auxiliary-agent substitution. Usage: /autopilot target.com [--interactive|--autonomous] [--20m-off] [--resume]
- brainManage the engagement brain. Subcommands: 'init' to set up, 'brief <target>' for pre-flight, 'status' for overview, 'exhausted [target]' to see dead ends.
- browser-agentBrowser automation agent for interactive web testing. Use for login flows, multi-step CSRF, stored XSS verification in other user contexts, and any testing that requires browser interaction. Requires Claude in Chrome MCP.
- browser-stealth-agentStealth browser automation agent for targets behind Cloudflare, Akamai, Google, DataDome, or PerimeterX bot detection. Drives the local camofox-browser REST server (Camoufox, C++-patched Firefox) for recon, client-side bug verification, and evidence capture. Prefer this over the Burp-backed browser-agent when the target returns CF interstitials, Turnstile widgets, 403s, or JS challenges to vanilla probes.
- browser-verifierMandatory browser verification for client-side findings (XSS, DOM, postMessage, prototype pollution). Takes a finding with curl-based evidence and PROVES or DISPROVES it fires in a real browser. No finding ships without browser verification. Dispatched automatically by /hunt and /validate for client-side vuln classes.
- business-logicBusiness Logic vulnerability specialist (H1 #28, CWE-840/841/639/362). Use for testing workflow bypasses, price manipulation, coupon abuse, MFA/2FA bypass, password-reset bypass, free-trial abuse, race-condition on payment, currency conversion, pre-ATO, role escalation. Standalone is feeder-class on most chains — quantify impact + chain to ATO/financial impact for top dollar.
- chainBuild deep exploit chains — dispatches chain-builder agent. Given bug A, recursively walks the chain graph. Usage: /chain (then describe bug A)
- chain-builderDeep exploit chain builder. Given bug A, recursively walks the chain graph — each confirmed link becomes the new A. No depth limit. Supports 2-link to 10+ link chains. Use when you have any finding that needs escalation.