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-cobalt-strike-trafficgit 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-cobalt-strike-traffic)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/hunting-cobalt-strike-traffic"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/hunting-cobalt-strike-traffic/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-cobalt-strike-traffic"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/hunting-cobalt-strike-traffic.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.00075 | $0.00689 |
| Opus 5 | $0.00037 | $0.00345 |
| Sonnet 5 | $0.00015 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
hunting-cobalt-strike-traffic 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 8d 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 Cobalt Strike Traffic
When to Use
- You have HTTP request logs (proxy/Zeek http.log) and/or process telemetry and want to detect default-configuration Cobalt Strike beacons.
- You are triaging suspected C2 using known default artifacts before deeper analysis.
Do not use default-indicator detection as proof — operators customize Malleable C2 profiles. Absence of defaults does not mean no Cobalt Strike. This skill parses telemetry and executes nothing.
Prerequisites
- HTTP request URIs and/or process/pipe telemetry.
Workflow
Step 1: Detect default stager URIs
python scripts/analyst.py hunt http.csv
Flags request URIs whose path matches the Cobalt Strike default stager checksum8 algorithm (sum of the path characters mod 256 equals 92 for x86 or 93 for x64 stagers).
Step 2: Match default profile artifacts
Flag default user-agents, default URIs (/__utm.gif, /submit.php, /pixel), and default named
pipes (\\.\pipe\msagent_*, \\.\pipe\status_*) when present in telemetry.
Step 3: Confirm
Corroborate with beaconing periodicity and destination reputation; pivot to memory/config analysis.
Step 4: Operationalize
Write detections for checksum8 URIs and known default artifacts, accepting they catch defaults only.
Validation
- checksum8 detection correctly computes the path-character sum mod 256.
- Default profile artifacts are matched exactly, not by loose substrings.
- Findings are presented as default-indicator hits, not definitive attribution.
Pitfalls
- Customized Malleable C2 profiles defeating all default-artifact checks.
- checksum8 false positives on unrelated short URIs — corroborate with other signals.
- Treating a single default hit as confirmation without behavioral corroboration.
References
- See
references/api-reference.mdfor the hunter. - ATT&CK S0154 Cobalt Strike (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.
- 8d ago First seen · 85 lines · 75 tokens per session scan A 5691445f7a46
hunting-cobalt-strike-traffic is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 689 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-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-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-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-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.