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 OpenLAIR/OpenSkill --skill evo-suricata-custom-exfilgit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/openlair/openskill/evo-suricata-custom-exfil)<a href="https://agentmods.dev/skills/openlair/openskill/evo-suricata-custom-exfil"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-suricata-custom-exfil/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/openlair/openskill/evo-suricata-custom-exfil"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-suricata-custom-exfil.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.00051 | $0.01272 |
| Opus 5 | $0.00026 | $0.00636 |
| Sonnet 5 | $0.00010 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
evo-suricata-custom-exfil 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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evo-suricata-custom-exfil
Description
Generates Suricata 7.0 rules for detecting data exfiltration hidden in HTTP telemetry traffic. Handles all five detection conditions with proper sticky buffer syntax, URL-decode transforms, parameter boundary awareness, and PCRE anchoring to minimize false positives and false negatives.
Domain Knowledge
Suricata 7.0 Rule Structure
- Header:
alert http any any -> any any— usealert httpto leverage Application Layer Protocol Identification (ALPI); avoids port-dependent matching. - Use
any any -> any anywhen both source and destination may be internal (e.g., 10.x to 10.x). - Options in parentheses, semicolon-delimited.
- Must include
sid,rev, and ideallyflow:established,to_server.
Sticky Buffers (Suricata 7.0)
Sticky buffers are context switches: once declared, all subsequent content, pcre, bsize,
depth, offset, distance, within keywords apply to that buffer until a new sticky buffer
is declared. This is the modern 7.0 approach — legacy trailing modifiers like http_method are
deprecated.
http.method;— matches HTTP verb (POST, GET, etc.)http.uri;— normalized URI including query string and leading/http.uri.raw;— unnormalized URI as on the wirehttp.header;— all request headers concatenated, CRLF-separatedhttp.request_header;— individual header, name and value joined by|3a 20|(:)http.request_body;— HTTP request body (POST/PUT/PATCH payload)
Critical Rules & Edge Cases
-
Sticky buffer ordering: Buffer keyword BEFORE content match. Correct:
http.method; content:"POST";Wrong:content:"POST"; http.method; -
Exact URI matching:
http.uriincludes query string. Usestartswith; endswith;to prevent substring matches (e.g.,/telemetry/v2/report/extra). -
Header matching options:
http.header;withcontent:"X-TLM-Mode"; content:"exfil";— works but risks cross-header false positives.http.request_header;withcontent:"X-TLM-Mode|3a 20|exfil";— isolates a single header, more precise. The|3a 20|is the colon-space separator Suricata normalizes.
What ships with it
1 file 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.
- yesterday First seen · 101 lines · 51 tokens per session scan A d624f7f570e2
evo-suricata-custom-exfil is a skill published in the GitHub repository OpenLAIR/OpenSkill (90 stars, last pushed 2d ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,272 once invoked, about $0.0003 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-11.
Other skills, from other repositories
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
experimental-design
Best practices for designing reproducible ML experiments. Use when planning ablations, baselines, or controlled experiments.
prolong
Recover and use durable coding-session history from PRO-LONG's local append-only log. Use on long-running coding tasks, after context compaction or session resume, when reconstructing prior decisions or tool results, or before repeating work that may already have been attempted.
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.
security-review
Use when reviewing code for vulnerabilities, checking diffs for injection/XSS/auth/crypto issues. Invokes on code changes (.go/.py/.js/.ts/.java/.rs/.php/.rb), not docs-only diffs.
script-exec-blocked
Sandbox approval policy blocks executecode and python3 -c; use readfile/writefile + manual transforms instead of retrying both runners.