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 meltedinhex/analyst-ai-pack --skill hunting-domain-fronting-and-cdn-abusegit clone --depth 1 https://github.com/meltedinhex/analyst-ai-packWrote 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/meltedinhex/analyst-ai-pack/hunting-domain-fronting-and-cdn-abuse)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/hunting-domain-fronting-and-cdn-abuse"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/hunting-domain-fronting-and-cdn-abuse/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/meltedinhex/analyst-ai-pack/hunting-domain-fronting-and-cdn-abuse"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/hunting-domain-fronting-and-cdn-abuse.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.00072 | $0.00665 |
| Opus 5 | $0.00036 | $0.00332 |
| Sonnet 5 | $0.00014 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
hunting-domain-fronting-and-cdn-abuse 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 9d 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
Hunting Domain Fronting and CDN Abuse
When to Use
- You have TLS/HTTP telemetry (Zeek ssl.log + http.log, proxy logs) and want to detect domain fronting, where the TLS SNI shows a benign CDN domain but the inner HTTP Host differs.
- You are hunting C2 hidden behind high-reputation CDNs.
Do not use SNI/Host mismatch as definitive — some legitimate setups differ. Corroborate with destination behavior and reputation.
Prerequisites
- Telemetry pairing TLS SNI with the inner HTTP Host (or proxy logs exposing both).
Workflow
Step 1: Detect SNI/Host mismatch
python scripts/analyst.py hunt flows.csv
Flags connections where the TLS SNI and HTTP Host headers resolve to different registered domains, especially when the SNI is a known CDN/fronting-capable domain.
Step 2: Surface CDN-hosted anomalies
Highlight high-reputation CDN SNIs carrying long-lived or beaconing flows.
Step 3: Confirm
Corroborate with beacon periodicity, JA3, and destination reputation; many CDN mismatches are benign.
Step 4: Operationalize
Write a detection for SNI/Host registered-domain mismatch on fronting-capable CDNs.
Validation
- Mismatch is computed on the registered domain, not the full hostname.
- Known CDN SNIs are recognized to prioritize fronting-capable cases.
- Findings are presented with corroboration needs, not as proof.
Pitfalls
- Legitimate multi-tenant CDN/edge configs producing benign mismatches.
- Encrypted SNI (ECH) hiding the SNI entirely — different hunt required.
- Treating any CDN traffic as suspicious (high false-positive rate).
References
- See
references/api-reference.mdfor the hunter. - ATT&CK T1090.004 and the TLS SNI RFC (linked in frontmatter).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 85 lines · 72 tokens per session scan A 79f6cf97bf98
hunting-domain-fronting-and-cdn-abuse is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 665 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
analyzing-cobalt-strike-beacon-configuration
Use when extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft. Use when working with analyzing cobalt strike beacon configuration.
analyzing-cobalt-strike-beacon-configuration
A guide to extracting and examining Cobalt Strike Beacon settings from Windows executable files or memory dumps. Cobalt Strike is a security testing tool often misused by attackers, and Beacon is its remotely controlled payload.
analyzing-malicious-pdf-with-peepdf
A Chinese-language skill for examining suspicious PDF files with peepdf, pdfid, and pdf-parser. It is intended for static malware analysis, which studies a file without running it.