Skip to content
SkillModel-led4,590 tokens in use

hunt-brute-force

A hunting guide for missing or weak rate limiting in authorized testing: OTP and login brute force, enumeration, IP-rotation bypass, token entropy and ReDoS.

14,523 stars on the repository MIT Licenseelementalsouls/Claude-BugHunter · skills/hunt-brute-force
/plugin marketplace add elementalsouls/Claude-BugHunter /plugin install claude-bughunter@elementalsouls
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing hunt-brute-force costs

148tokens idle
4,590tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectednetworkdetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 70
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 73

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance84
  • Community68
  • Maturity28
  • Momentum40

hunt-brute-force is a skill for Claude covering missing or weak rate limiting, built from published technique classes. It treats OTP and password-reset brute force, login credential stuffing, username and email enumeration, coupon and gift-card brute force, and ReDoS as one family of findings.

The skill’s central contribution is a four-state classification of rate-limit defenses (hard lockout, soft IP throttle, CAPTCHA injection, and a silent shadow-throttle that a naive test misses), a seeded test that distinguishes a shadow-throttle from an open endpoint, and methods for IP-rotation bypass, timing-based enumeration, and measuring token entropy with a tool. It is for assets covered by a program or engagement you are authorized to test.

What You Get

  • A four-state classification of rate-limit defenses, including a seeded test for silent shadow-throttling that a status-code-only check misses
  • A phased method covering login rate limits, OTP/2FA brute force, enumeration (string, status and timing), IP-rotation bypass via spoofable headers, token entropy measurement, and ReDoS detection
  • Request snippets for ffuf, hydra and nuclei tuned for rate-limit and default-credential testing
  • A chain table mapping each finding to its likely severity, from account takeover down to informational
  • A validation checklist that requires reachability math for full-keyspace claims and reproducible deltas for enumeration and IP-bypass findings

Common Use Cases

  • Testing whether an OTP or 2FA verification endpoint enforces an effective limit across its full numeric keyspace
  • Checking whether a login or password-reset endpoint can be rate-limit-bypassed by rotating X-Forwarded-For and similar headers
  • Measuring the entropy of a password-reset or session token to see whether it is predictable within its validity window

What Makes It Unique

Most rate-limiting checks stop at whether a 429 appears. This skill’s four-state model names the case where a server returns 200/401 for every request while silently dropping the submissions that would succeed, and gives a seeded known-good probe to detect that case directly. It also ties severity for a brute-force claim to measured throughput against keyspace size, not a short probe.

Under The Hood

The skill is a single SKILL.md of guidance with no bundled scripts. Following it, the agent sends bursts of HTTP requests to login, OTP-verification, password-reset and registration endpoints, measuring status code, response latency and body size across many requests, and may run external tools such as ffuf, hydra, nuclei and Burp Sequencer against those endpoints. It writes intermediate output such as collected tokens to the working folder for entropy analysis. Use it only against assets you are authorized to test.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers