Assemble a reproducible, minimal, tamper-evident evidence bundle for a security finding, preserving provenance and separating observed facts from interpretation.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Transform verifier outputs into an auditable evidence bundle that triage and report-writing agents can rely on without reconstructing or exaggerating the finding.
This skill packages evidence; it does not invent missing evidence or raise severity.
Record target, revision, branch, contract address/network where applicable, build flags, deployment profile, and authorized test environment.
For every report claim, link the minimum evidence that supports it. Classify claims:
OBSERVED — directly recorded;DERIVED — calculated from recorded evidence;INFERRED — logically supported but not directly observed;UNVERIFIED — unsupported and must not appear as fact.Each artifact records:
Never alter raw evidence. Store sanitized copies separately and document redactions.
Remove or mask credentials, personal data, private keys, session tokens, unrelated tenant data, and production secrets. Preserve only the minimum necessary proof. Do not package live exploit credentials.
Provide deterministic steps:
Examples:
Negative controls help prove causality.
A report-ready package needs:
Use templates/evidence-manifest.yaml. Suggested directory layout is in references/bundle-layout.md.
REPORT_READYTECHNICALLY_VERIFIED_IMPACT_INCOMPLETEREPRODUCTION_INCOMPLETEPROVENANCE_INCOMPLETESENSITIVE_DATA_REVIEW_REQUIREDNOT_READYNever fabricate screenshots, logs, hashes, request IDs, transaction hashes, line numbers, success rates, or environment details. Missing data must remain explicitly missing.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Provide comprehensive techniques for testing REST, SOAP, and GraphQL APIs during bug bounty hunting and penetration testing engagements. Covers vulnerability discovery, authentication bypass, IDOR exploitation, and API-specific attack vectors.
The English summary is being prepared. Showing the original description.
Web2 attack chain plugin — apply Web2 trust boundaries and composition rules on top of attack-chaining-core for authorized testing of web apps, APIs, identity, cloud, and internal services.
The English summary is being prepared. Showing the original description.
Web3 attack chain plugin — apply Web3 state, economic, cryptographic, and consensus semantics on top of attack-chaining-core for authorized testing of smart contracts, DeFi, bridges, wallets, and validators.
The English summary is being prepared. Showing the original description.
Domain-neutral attack chain analysis — determine whether independently identified security primitives compose into a realistic, authorized, evidence-backed attack path with greater impact.
The English summary is being prepared. Showing the original description.
Build an evidence-backed map of externally and internally reachable attack surfaces, trust boundaries, privileged transitions, security assets, and high-value audit targets before vulnerability hunting.
The English summary is being prepared. Showing the original description.
Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking "what should I do next" or "where am I in the process."
The English summary is being prepared. Showing the original description.