Skip to content

Garyson26/Trident-SecOps-Skills / skills/bug-bounty-workflow

bug-bounty-workflow

Verified

Bug bounty workflow skill for program scope mapping, recon-to-report automation, deduplication against prior submissions, and high-signal reporting on HackerOne, Bugcrowd, Intigriti, YesWeHack, and self-hosted programs. Use to organize bounty work end to end while staying inside program rules.

Bug Bounty Workflow

Program Rules First

  • Parse and pin the program brief: in-scope, out-of-scope, allowed techniques, rate, retesting, safe harbor, disclosure.
  • Refuse any step that violates program rules or applicable law, even if technically possible.
  • Track per-target state so you never test out-of-scope assets accidentally.

Workflow

  1. Scope ingest: domains, mobile apps, APIs, source repos, partner services; tag each with in/out/maybe and rate.
  2. Recon: passive OSINT, subdomain/asset discovery, screenshot, tech fingerprint, content discovery; store as snapshots.
  3. Triage surface: prioritize high-value endpoints (auth, payments, admin, file upload, SSO, webhook, API gateway).
  4. Test: auth/authorization, IDOR, SSRF, RCE, business logic, secrets exposure, race conditions; minimize impact.
  5. Reproduce cleanly: minimal steps, no extra access, redacted PoC, controlled test accounts.
  6. Dedupe: search prior public disclosures, hacker activity, changelogs; cross-check internal notes.
  7. Report: clear title, severity rationale (CVSS + program rubric), impact narrative, reproduction, remediation.

Quality Bar

  • One vulnerability per report. Chain only when chaining is the bug.
  • Include log/HTTP evidence with secrets redacted, plus suggested fix and detection.
  • Offer collaborative retest after the fix.

Output Contract

  • programs/<name>/scope.yaml, recon/, notes.md, reports/<id>.md, metrics.csv (submissions, accepted, paid, dupes).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall