agentleFS
Sign inStart free
mtarcuremtarcure/claude-vibe-squad/.agents/skills/detection-as-code/SKILL.md

detection-as-code

Skill220 starsChanged 16 days agoMITView on GitHub

Use when a detection engineer must author a Sigma, YARA, KQL, or SPL SIEM/EDR rule for a named TTP—pin the telemetry schema, add must-fire and must-not-fire fixtures, and replay representative history before any gated rollout. Not for incident triage or source-code defect scanning.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the rule against real field names.

    line 13
  2. Distinctive:

    Add positive fixtures (must fire) and negative fixtures (must not over-fire).

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Detection as Code

Author a SIEM/EDR detection rule as tested, versioned code (Sigma/YARA/KQL/SPL).

Steps

  1. State the target TTP, detection platform, and platform/schema version; confirm the telemetry prerequisites exist.
  2. Write the rule against real field names; keep attacker-TTP modelling strictly in service of detection.
  3. Add positive fixtures (must fire) and negative fixtures (must not over-fire); validate syntax.
  4. Backtest/replay against representative history; record expected FP/FN surface and rule cost/cardinality.
  5. Set rollout mode, owner, version, and rollback; deployment is operator-gated (production_mutation).

Acceptance

  • Positive fixture fires and negative fixture does not; syntax validated.
  • Replay/backtest evidence present, or an explicit unvalidated status.
  • Owner, version, and rollback recorded; no live deploy without approval.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free