Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Samurai-goose/SPECTER-The-Illusive-Security-Protocol --skill active-directory-and-identity-auditgit clone --depth 1 https://github.com/Samurai-goose/SPECTER-The-Illusive-Security-ProtocolWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/active-directory-and-identity-audit)<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/active-directory-and-identity-audit"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/active-directory-and-identity-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/active-directory-and-identity-audit"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/active-directory-and-identity-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.01872 |
| Opus 5 | $0.00019 | $0.00936 |
| Sonnet 5 | $0.00008 | $0.00374 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
active-directory-and-identity-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Active Directory & Identity Audit
Purpose
Assess enterprise identity infrastructure — Active Directory, LDAP, Azure AD/Entra ID, and associated identity providers — for privilege escalation paths, Kerberos weaknesses, misconfigured trusts, excessive permissions, and credential exposure. Covers both on-premises AD and cloud identity (Azure AD, Okta, etc.).
Triggers
- Enterprise environment with Active Directory in scope
- Azure AD / Entra ID tenant authorized for testing
- User requests AD security audit
- Recon identifies domain-joined systems or LDAP services
- Credential discovered during other assessment phase
Required Inputs
| Input | Description | Required |
|---|---|---|
governance_context |
Active engagement governance record | Yes |
target_domain |
AD domain(s) or tenant in scope | Yes |
access_level |
Current credentials/access (domain user, local admin, etc.) | Yes |
environment |
On-prem AD, Azure AD, hybrid, Okta, etc. | Yes |
tools_available |
BloodHound, PowerView, Impacket, ADExplorer, etc. | Recommended |
Workflow
-
Scope Verification — Confirm AD domain/tenant and testing boundaries.
-
Domain Reconnaissance
- Enumerate domain controllers, functional level, trusts
- Map organizational units (OUs) and Group Policy structure
- Enumerate users, groups, computers, service accounts
- Identify privileged groups: Domain Admins, Enterprise Admins, Schema Admins, Account Operators, Backup Operators
- Map group nesting and effective memberships
- Enumerate SPNs (Service Principal Names) for Kerberoasting targets
- Identify accounts with no pre-authentication (AS-REP Roasting)
- Enumerate password policies and fine-grained password policies
- Map trust relationships (forest, domain, external, realm)
-
Kerberos Attack Surface
Attack Condition Impact Kerberoasting Service accounts with SPNs Offline password cracking of service accounts AS-REP Roasting Accounts with DONT_REQUIRE_PREAUTHOffline password cracking without auth Golden Ticket KRBTGT hash compromised Persistent domain-level access Silver Ticket Service account hash Forged service ticket, impersonation Constrained Delegation msDS-AllowedToDelegateTo set Impersonate any user to delegated service Unconstrained Delegation TrustedForDelegation flag Capture TGTs of connecting users Resource-Based Constrained Delegation (RBCD) Write access to msDS-AllowedToActOnBehalfOfOtherIdentity Privilege escalation via delegation Pass-the-Ticket Ticket extracted from memory Lateral movement without password Overpass-the-Hash NTLM hash available Request Kerberos ticket using NT hash Diamond Ticket KRBTGT AES key Undetectable persistence
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 187 lines · 39 tokens per session scan A 1399c60d2677
active-directory-and-identity-audit is a skill published in the GitHub repository Samurai-goose/SPECTER-The-Illusive-Security-Protocol (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,872 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…