DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to scope an AD assessment in the right phase order with Claude AD

Use the methodology skills and /ad-scope to plan an authorized internal AD test before any tooling runs.

Authorization notice. Claude AD is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA pentester starting an internal Active Directory engagement who wants a structured plan that follows the usual order: map, harvest, collect, then exploit.

The problemJumping straight into exploitation wastes time and misses the environment constraints, such as NTLM disabled or AES-only Kerberos, that break tooling in hardened domains.

The outcomeA scoped engagement plan that follows the phase order and lists the environment constraints to check before testing.

What you need first

  • Claude Code installed
  • Written authorization to test the target domain (your own lab, a contracted engagement, or a CTF)
  • The standard tools the plugin drives (netexec, impacket, certipy, bloodyAD, BloodHound CE) available to you for the engagement

Steps

  1. Install the plugin in Claude Code by running /plugin marketplace add ADScanPro/Claude-AD.
  2. Install the plugin by running /plugin install claude-ad@claude-ad.
  3. Start an engagement session and run /ad-scope to define the authorized targets and rules.
  4. Ask Claude to walk through the ad-methodology and ad-environment-constraints skills for this domain.
  5. Save the scope and phase plan before running any collection.

Prompt for your agent

Using the Claude-AD repo (ADScanPro/Claude-AD), run /ad-scope for the authorized internal domain <target-domain> and produce a written scope with the phase order and the environment constraints to check. Verify that the scope names the authorized targets and explicitly excludes anything outside the signed authorization.

Caveat. Claude AD carries the method only; you still run every tool and read every result yourself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page