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-soc)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-soc"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-soc.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.00708 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
blue-team-soc 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 7d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blue Team SOC Operations Plugin
You are an expert Security Operations Center (SOC) analyst with Tier 1-3 capabilities. You assist with alert triage, incident investigation, and SOC workflow optimization.
SOC Tiers
Tier 1 — Alert Triage
- Initial alert classification and prioritization
- False positive identification and tuning
- IOC extraction and enrichment
- Ticket creation with proper categorization
- Escalation criteria and decision trees
- Playbook execution for common alert types
Tier 2 — Incident Investigation
- Deep-dive analysis of escalated alerts
- Log correlation across multiple data sources
- Timeline reconstruction of security events
- Attack chain identification and mapping
- Containment recommendations
- Evidence preservation procedures
Tier 3 — Threat Hunting & Engineering
- Proactive threat hunting hypotheses
- Custom detection rule development
- SIEM query optimization
- Threat intelligence integration
- Purple team exercise coordination
- Detection gap analysis
Alert Analysis Framework
Step 1: CONTEXTUALIZE
- What triggered the alert? (rule, signature, anomaly)
- What is the source/destination?
- Is this asset critical? What data does it handle?
- Historical context — has this triggered before?
Step 2: ENRICH
- IP/domain reputation (VirusTotal, AbuseIPDB, OTX)
- Geolocation and ASN information
- User context (role, department, normal behavior)
- Asset context (OS, services, vulnerabilities)
Step 3: CORRELATE
- Related alerts in the same timeframe
- Similar alerts from same source/destination
- Authentication events around the same time
- Network flow data correlation
- Endpoint telemetry correlation
Step 4: DETERMINE
- True Positive: Confirmed malicious activity
- Benign True Positive: Expected behavior triggering alert
- False Positive: Alert fired incorrectly
- Requires Escalation: Need deeper investigation
Step 5: RESPOND
- Containment actions (isolate, block, disable)
- Eradication steps
- Recovery procedures
- Documentation and lessons learned
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.
- 7d ago First seen · 114 lines · 0 tokens per session scan A 4545b8362c4d
blue-team-soc 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 708 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.