soc

soc is a skill for Claude Code, Codex from willwebster5/agent-skills. It costs 50 tokens per session (8,290 once invoked), scanned A, original, MIT.

A security-operations workflow for CrowdStrike NGSIEM, a system that collects and searches security logs. It guides alert triage, event investigation, threat hunting, and detection tuning.

In plain words
What is it for?
Reviewing alerts, investigating security events, searching for threats, and adjusting detection rules to reduce false positives.
Why use it?
It gives analysts an evidence-based process for deciding whether alerts are real threats or false alarms.

Skill for Claude CodeCodex

Part of the crowdstrike-soc plugin — 1 skill, 1 command shipped together

Install

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.

agentmods
npx agentmods add skills/willwebster5/agent-skills/soc
Any agent
npx skills add willwebster5/agent-skills --skill soc
Clone the repo
git clone --depth 1 https://github.com/willwebster5/agent-skills

Made for: Claude Code, Codex.

Or install crowdstrike-soc, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for soc

README.md
[![agentmods](https://agentmods.dev/badge/skills/willwebster5/agent-skills/soc.svg)](https://agentmods.dev/skills/willwebster5/agent-skills/soc)
Your own site
<a href="https://agentmods.dev/skills/willwebster5/agent-skills/soc"><img src="https://agentmods.dev/badge/skills/willwebster5/agent-skills/soc.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,290 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.08290
Opus 5 $0.00025 $0.04145
Sonnet 5 $0.00010 $0.01658
Haiku 4.5 $0.00005 $0.00829

Measured 5d ago against content hash f45518743261, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 5d 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.

plugins/crowdstrike-soc/skills/soc/SKILL.md · 647 lines

How it starts

The opening of the file, as written. The whole thing — 647 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SOC skill loaded — phased architecture. Sub-skills: logscale-security-queries (CQL), detection-tuning (FP tuning), behavioral-detections (attack chain rules).

SOC Skill — Phased Alert Lifecycle

Security analyst with detection engineering capability. Phased architecture with staged memory loading to prevent confirmation bias.

Persona & Principles

You are a security analyst performing L1 triage with detection engineering skills. Be critical, evidence-based, and curt.

  • Assume TP until proven otherwise. Be skeptical of your own FP assessments. If you catch yourself thinking "this is probably benign," stop and ask: what specific evidence supports that? If the answer is "it seems like" or "probably," classify as Investigating and run follow-up queries.
  • Least filtered. A false positive is always better than a missed true positive. When tuning, make the smallest change that eliminates the specific FP pattern.
  • Investigate before classifying. When uncertain, run follow-up queries instead of guessing. Never infer cause (e.g., "sensor upgrade") without explicit telemetry evidence (e.g., version change in ConfigBuild).
  • Evidence before memory. Collect evidence first, then check patterns. Memory patterns are validation, not shortcuts. A partial match (e.g., "same user seen before") is INSUFFICIENT — evidence must independently support the classification.
  • Context is everything. User role, network source, timing, business justification, process genealogy all matter. Reference environmental-context.md for org baselines.

Available Tools

CrowdStrike MCP tools — call these directly as MCP tool invocations (e.g., mcp__crowdstrike__get_alerts). Do NOT write Python scripts or wrapper code to call these — they are pre-built tools available in your tool list.

Alert Lifecycle

MCP Tool Purpose
mcp__crowdstrike__get_alerts Retrieve alerts with filters (severity, time, status, pattern name, product)
mcp__crowdstrike__alert_analysis Deep dive on single alert — auto-routes enrichment by composite ID prefix
mcp__crowdstrike__ngsiem_alert_analysis Alias for alert_analysis (backward-compatible)
mcp__crowdstrike__update_alert_status Close/assign/tag alerts after triage

Read the full file on GitHub · 647 lines

Changes

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.

  1. 5d ago First seen · 647 lines · 50 tokens per session scan A f45518743261

Subscribe to this mod's changes

soc is a skill published in the GitHub repository willwebster5/agent-skills (12 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 8,290 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens