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 agentmods add skills/kalpmodi/akira/ad-attacksnpx skills add kalpmodi/akira --skill ad-attacksgit clone --depth 1 https://github.com/kalpmodi/akiraWrote 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/kalpmodi/akira/ad-attacks)<a href="https://agentmods.dev/skills/kalpmodi/akira/ad-attacks"><img src="https://agentmods.dev/badge/skills/kalpmodi/akira/ad-attacks.svg" alt="Measured on agentmods" 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.00095 | $0.00381 |
| Opus 5 | $0.00048 | $0.00191 |
| Sonnet 5 | $0.00019 | $0.00076 |
| Haiku 4.5 | $0.00010 | $0.00038 |
Grade A, and why
ad-attacks 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 6d 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.
What it actually says
Active Directory Attacks - Redirect Stub
AD attack TTPs have been consolidated into the redteam skill, which is the canonical source for all AD, post-exploitation, lateral movement, and APT simulation techniques.
Immediately invoke:
/redteam <target> --focus=ad
The --focus=ad flag tells redteam to prioritize:
- BloodHound collection and shortest-path analysis
- Kerberoasting + AS-REP roasting
- LDAP enumeration (null session -> authenticated)
- Pass-the-Hash / Pass-the-Ticket chains
- ADCS ESC1-ESC8 certificate abuse
- Constrained/unconstrained delegation + RBCD
- DCSync + DCShadow
- GPO abuse + ACL abuse (T1484 / T1222)
- Golden/Silver ticket forge
- Domain compromise - NTDS.dit extraction
All techniques are documented in ~/.claude/skills/redteam/SKILL.md under Classes RT04, RT05, RT05b, RT05c.
For full APT kill chain (C2, LotL, AMSI bypass, persistence, defense evasion, cloud APT, exfil, OPSEC) run /redteam <target> without the focus flag after obtaining a foothold.
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.
- 6d ago First seen · 31 lines · 95 tokens per session scan A ea74fc0ed263
ad-attacks is a skill published in the GitHub repository kalpmodi/akira (21 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 381 once invoked, about $0.0005 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-30.
Other skills, from other repositories
performing-aws-privilege-escalation-assessment
Performing authorized privilege escalation assessments in AWS environments to identify IAM misconfigurations that allow users or roles to elevate their permissions using Pacu, CloudFox, Principal Mapper, and manual IAM policy analysis techniques.
performing-cloud-penetration-testing-with-pacu
Performing authorized AWS penetration testing using Pacu, the open-source AWS exploitation framework, to enumerate IAM configurations, discover privilege escalation paths, test credential harvesting, and validate security controls through systematic attack simulation.
conducting-cloud-penetration-testing
This skill outlines methodologies for performing authorized penetration testing against AWS, Azure, and GCP cloud environments. It covers understanding the shared responsibility model for testing scope, leveraging cloud-specific attack tools like Pacu and ScoutSuite, exploiting IAM misconfigurations, testing for SSRF…
performing-kubernetes-penetration-testing
Kubernetes penetration testing systematically evaluates cluster security by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policies, and secrets. Using tools.
conducting-full-scope-red-team-engagement
Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities.
llm-prompt-injection
Use when testing an authorized LLM application for prompt injection, system-prompt exposure, unsafe tool use, or RAG data-boundary failures.