Skip to content
SkillModel-led3,089 tokens in use

hunt-ato

A taxonomy of nine account takeover paths for authorized testing, from password reset flaws and email change to OAuth linking and JWT weaknesses, with proof on a second test account.

14,523 stars on the repository MIT Licenseelementalsouls/Claude-BugHunter · skills/hunt-ato
/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-ato costs

243tokens idle
3,089tokens 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

shelldetectednetworkdetected

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 →
Good
  • Frontmatter12/15
  • Structure17/25
  • Examples12/15
  • Output15/15
  • Size13/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 13
  • Reaches the network−10

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

    SKILL.md, line 69

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-ato is a skill for Claude that organizes account takeover testing into nine paths. They include password reset flaws (host-header handling, predictable or reusable tokens, token leaks through Referer), email change without re-authentication, OAuth account linking, session handling, JWT weaknesses, recovery questions and chained cases such as a dangling subdomain used with OAuth redirects.

The skill treats takeover as a destination reached by several primitives. Each path becomes a reportable finding only when it is shown against a second test account from a separate session, and the skill lists checks that rule out false positives, such as reading the delivered email to see which link domain the server really sends. It is for assets in scope of a program or engagement.

What You Get

  • Nine takeover paths with the observable signs of each
  • A proof standard based on two test accounts and out-of-band confirmation
  • False-positive checks such as reading the delivered email and capturing outbound requests in the network tab
  • Notes on JWT, recovery-question and OAuth redirect weaknesses
  • Chain ideas that connect takeover with subdomain and open-redirect findings

Common Use Cases

  • Reviewing a password reset flow on an in-scope application
  • Checking that email and password changes ask for current credentials
  • Judging whether a low-severity redirect or token leak can be shown as a full takeover

What Makes It Unique

It treats account takeover as an outcome with many routes and ties each route to a proof requirement, which reduces reports that rest on reflected headers alone. It keeps the routes together in one skill so one test session can cover reset, session, OAuth and token paths.

Under The Hood

The skill is a single SKILL.md of guidance with no bundled scripts. Following it, the agent sends HTTP requests to reset, login and recovery endpoints of the target in scope, may set up out-of-band callbacks to confirm delivery, and may repeat requests to check rate limits on codes and recovery answers. It may write notes to the working folder. The text includes request snippets, token-handling examples and brute-force patterns as teaching material. Use it only with accounts and applications 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