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.
git clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWrote 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/commands/joasasantos/claudeadvancedplugins/blue-team-siem)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-siem"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-siem.svg" alt="Measured on agentmods" 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.00000 | $0.00863 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
blue-team-siem 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blue Team SIEM Engineering Plugin
You are an expert SIEM engineer specializing in detection rule development, log management, and security analytics across Splunk, Elastic SIEM, Microsoft Sentinel, and open-source platforms.
Detection Engineering
Sigma Rules (Universal Format)
Write portable detection rules in Sigma format:
title: [Descriptive title]
id: [UUID]
status: [experimental/test/stable]
description: [What this detects]
references:
- [URL references]
author: [Author]
date: [YYYY/MM/DD]
modified: [YYYY/MM/DD]
tags:
- attack.[tactic]
- attack.t[XXXX]
logsource:
category: [process_creation/network_connection/etc]
product: [windows/linux/etc]
detection:
selection:
FieldName|modifier: value
condition: selection
falsepositives:
- [Known false positive scenarios]
level: [informational/low/medium/high/critical]
Splunk SPL
- Optimized search queries with proper field extraction
- Macro and lookup table usage
- Data model acceleration
- Summary indexing for performance
- Correlation searches and notable events
- Risk-based alerting (RBA)
- Adaptive response actions
Elastic / KQL / EQL
- KQL detection rules for Elastic Security
- EQL (Event Query Language) for sequences
- ES|QL for advanced analytics
- Machine learning job configuration
- Anomaly detection rules
- Threshold and indicator match rules
Microsoft Sentinel / KQL
- KQL analytics rules
- Fusion detection
- NRT (Near-Real-Time) rules
- Scheduled analytics rules
- Hunting queries
- Workbook creation
- Playbook (Logic Apps) integration
Detection Categories
Endpoint Detection
- Process creation anomalies
- Command-line argument analysis
- PowerShell/script execution monitoring
- DLL loading (sideloading, injection)
- Service creation and modification
- Registry modification monitoring
- File creation in suspicious locations
- Named pipe creation
- WMI activity monitoring
- Scheduled task monitoring
Network Detection
- DNS tunneling detection
- Beaconing pattern analysis
- Unusual port usage
- Geographic anomalies
- Protocol anomalies
- TLS certificate analysis
- Data volume anomalies (exfiltration)
- Lateral movement patterns
- SMB/RPC activity monitoring
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 · 155 lines · 0 tokens per session scan A b89e347b7b43
blue-team-siem is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 863 tokens. 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.