Опишете задачата
Към всички skills

bb-methodology

awarexone · Разработка

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.

Оригинален текст · няма потвърден превод на български
Платформи: Не са посочениНиво: Не е посоченоВ индекса: 21.09.2026 г.Обновен в GitHub: 21.09.2026 г.

Теми: ai-security · bug-bounty · bugcrowd · claude-ai · claude-code · cti · ethical-hacking · hackerone · hacking · hacking-tool · penetration-testing · recon · vulnerability-scanner

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
5142
Лиценз
MIT
Последна проверка на записа
21.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add awarexone/Agentic-Bug-Hunter

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

Bug Bounty Methodology: Workflow + Mindset

Master orchestrator for hunting sessions. Combines the 5-phase non-linear workflow with the critical thinking framework that separates top 1% hunters from the rest.

PART 1: MINDSET (How to Think)

Core Principle

Hunting is not "find a bug" -- it is "prove an attack scenario." Think like an attacker with a specific goal, not a scanner looking for patterns.

Daily Discipline: Define, Select, Execute

Before touching any tool:

  1. Define: "Today I target [feature/domain] to achieve [CIA impact]"
  2. Select: Choose 1-2 vuln classes (IDOR, Race Condition, etc.)
  3. Execute: Focus ONLY on selected techniques. No wandering.

5 Ultimate Goals (Pick One Per Session)

  1. Confidentiality -- steal data the attacker shouldn't see
  2. Integrity -- modify data the attacker shouldn't change
  3. Availability -- disrupt service (app-level DoS only)
  4. Account Takeover -- control another user's account
  5. RCE -- execute commands on the server

4 Thinking Domains

1. Critical Thinking (deep analysis)

Question trust boundaries:

  • Frontend control disabled? Send request directly via proxy
  • user_role=user cookie? Change to admin
  • price=1000 in POST? Change to 1
  • <script> blocked? Try <img onerror=...>

Reverse-engineer developer psychology:

  • Feature A has auth checks -> Similar feature B (newly added) probably doesn't
  • Complex flows (coupon + points + refund) -> Edge cases have bugs
  • /api/v2/user exists -> Does /api/v1/user still work with weaker auth?

What-If experiments:

  • Skip checkout -> hit /checkout/success directly
  • Skip 2FA -> navigate to /dashboard
  • Send coupon request 10x simultaneously -> Race condition?
  • Replace guid=f8a2... with id=100 on sibling endpoint -> IDOR?

2. Multi-Perspective (multiple angles)

PerspectiveWhat to check
Horizontal (same role)User A's token + User B's ID -> IDOR
Vertical (different role)Regular user -> /admin/deleteUser
Data flow (proxy view)Hidden params in JSON: debug=false, discount_rate
Time/StateRace conditions, post-delete session reuse
Client environmentMobile UA -> legacy API with weaker auth
Business impact"What's the $ damage if this breaks?"

3. Tactical Thinking (pattern detection)

Целият SKILL.md в GitHub