agentleFS
Sign inStart free
Roshu18Roshu18/bearstrike-ai/skills/research-notes/SKILL.md

research-notes

Skill4 starsChanged 8 months agoMITView on GitHub

Practical bug bounty methodology notes derived from recent public security reports and training resources.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. ethicalcapital/skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to guide planning and triage decisions before running tools.

    line 8
  2. Distinctive:

    Start with low-noise recon and endpoint intelligence.

    line 26
  3. Distinctive:

    Keep one active hypothesis at a time until impact is confirmed.

    line 28
  4. Distinctive:

    Use async jobs for expensive tools to avoid MCP timeout loops.

    line 29
  5. Distinctive:

    Prefer context-aware payload sets (top 10 per class), not brute-force payload dumps.

    line 30
  6. Distinctive:

    Run constrained vulnerability templates and targeted payloads.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

research-notes

Use this skill to guide planning and triage decisions before running tools.

Last-30-day high-signal patterns

  • Access-control flaws remain top impact class (IDOR/BOLA, role boundary bypass).
  • API auth/session confusion appears in GraphQL and invite/workspace workflows.
  • SSRF remains high-impact where URL fetch parameters exist (swaggerUrl-style handlers).
  • Misconfiguration leaks (Prometheus /metrics, debug/internal endpoints) provide chainable recon intel.
  • Upload handling gaps (SVG script payloads) continue to produce stored XSS.

Frequent endpoint and parameter patterns

  • Endpoint families: /api/v1/, /api/auth, /api/user, /internal, /graphql, /metrics, /verify-otp.
  • Sensitive parameters: user_id, account_id, id, redirect_url, swaggerUrl.
  • Trust-boundary headers: custom session blobs, X-Original-URL, X-Forwarded-*.

Operational guidance for MCP AI

  • Start with low-noise recon and endpoint intelligence.
  • Prioritize account-boundary tests before aggressive scanning.
  • Keep one active hypothesis at a time until impact is confirmed.
  • Use async jobs for expensive tools to avoid MCP timeout loops.
  • Prefer context-aware payload sets (top 10 per class), not brute-force payload dumps.

Priority bug classes

  • IDOR/BOLA and role boundary bypass
  • auth/session handling flaws and OTP-flow bypass
  • API overexposure and mass assignment patterns
  • SSRF/open redirect request-routing issues
  • high-confidence misconfiguration exposures

Recommended triage sequence

  1. Map live hosts and key endpoints.
  2. Score endpoints and test high-priority routes first.
  3. Execute access-control and auth boundary checks.
  4. Run constrained vulnerability templates and targeted payloads.
  5. Escalate to deeper scans only when signals are strong.

Public references

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free