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 agentmods add skills/willwebster5/agent-skills/socnpx skills add willwebster5/agent-skills --skill socgit clone --depth 1 https://github.com/willwebster5/agent-skillsWrote 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/willwebster5/agent-skills/soc)<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>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 | $0.00050 | $0.08290 |
| Opus 5 | $0.00025 | $0.04145 |
| Sonnet 5 | $0.00010 | $0.01658 |
| Haiku 4.5 | $0.00005 | $0.00829 |
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.
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.mdfor 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 |
What ships with it
17 files 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.
- DESIGN.md 8.7 KB
- environmental-context.md 2.8 KB
- evals/v2-evals.json 8.2 KB
- memory/detection-ideas.md 728 B
- memory/fast-track-patterns.md 1.1 KB
- memory/fp-patterns.md 1.8 KB
- memory/investigation-techniques.md 1.6 KB
- memory/tp-patterns.md 940 B
- memory/tuning-backlog.md 808 B
- memory/tuning-log.md 593 B
- playbooks/cloud-security-aws.md 13 KB
- playbooks/container-sensor-investigation.md 9.3 KB
- playbooks/entraid-risky-signin.md 13 KB
- playbooks/entraid-signin-alert.md 7.1 KB
- playbooks/knowbe4-phisher.md 9.9 KB
- playbooks/README.md 7.6 KB
- tuning-bridge.md 7.2 KB
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.
- 5d ago First seen · 647 lines · 50 tokens per session scan A f45518743261
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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.
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…