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 writing-suricata-and-snort-rulesgit 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/writing-suricata-and-snort-rules)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/writing-suricata-and-snort-rules"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/writing-suricata-and-snort-rules/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/writing-suricata-and-snort-rules"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/writing-suricata-and-snort-rules.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.00082 | $0.00734 |
| Opus 5 | $0.00041 | $0.00367 |
| Sonnet 5 | $0.00016 | $0.00147 |
| Haiku 4.5 | $0.00008 | $0.00073 |
Grade A, and why
writing-suricata-and-snort-rules 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Suricata and Snort Rules
When to Use
- You need to author IDS rules to detect C2 traffic, malware downloads, or exploit attempts from observed network indicators.
- You want to validate rule syntax and avoid the patterns that cause false positives or silent non-matching.
Do not use broad content matches on common substrings that will flood alerts — anchor with
flow direction, ports, offsets, and uniqueness. This skill builds and lints rules; deploy them
through your IDS change process.
Prerequisites
- The indicators to detect (URI, host header, TLS SNI/JA3, byte pattern) and a target IDS (Suricata or Snort).
Workflow
Step 1: Draft the rule
Choose action, protocol, addresses/ports, direction, and a unique msg, sid, and rev. Add
content/pcre matches anchored with http.uri, tls.sni, flow:established,to_server, and
offsets/depths.
Step 2: Lint the rule
python scripts/analyst.py lint rules.rules
Checks for required fields (msg, sid, rev, classtype), balanced quotes/parentheses,
non-anchored overly short content, and duplicate SIDs.
Step 3: Tune to reduce noise
Add threshold/detection_filter, flowbits, and specific buffers (http.host, dns.query)
to scope matches.
Step 4: Document and stage
Record what each rule detects and stage it for testing against a pcap before production.
Validation
- Every rule has
msg, a uniquesid, and arev. contentmatches are anchored (buffer/offset/flow) rather than free-floating short strings.- Rules parse without unbalanced quotes/parentheses.
Pitfalls
- Free-floating
content:"GET"style matches creating massive false positives. - Duplicate or reused SIDs causing rule-load conflicts.
- Forgetting
flow:establishedand matching on unrelated traffic directions.
References
- See
references/api-reference.mdfor the linter. - Suricata and Snort rule docs (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 · 90 lines · 82 tokens per session scan A 54cf433a0486
writing-suricata-and-snort-rules is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 734 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…
Network Security & Traffic Analysis
Network traffic analysis, PCAP parsing, IDS/IPS rule creation, firewall configuration auditing, and network anomaly detection.
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.
yara-rule-writing-malware
Write custom YARA rules to identify and classify malware based on textual and binary patterns. This skill focuses on creating robust signatures using strings, regular expressions, and hexadecimal opcodes extracted during malware analysis for enterprise threat hunting.