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 skills add willwebster5/agent-skills --skill soc-agentsgit 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-agents)<a href="https://agentmods.dev/skills/willwebster5/agent-skills/soc-agents"><img src="https://agentmods.dev/badge/skills/willwebster5/agent-skills/soc-agents.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.00054 | $0.08880 |
| Opus 5 | $0.00027 | $0.04440 |
| Sonnet 5 | $0.00011 | $0.01776 |
| Haiku 4.5 | $0.00005 | $0.00888 |
Grade A, and why
soc-agents 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 6d 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 — 686 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOC skill v3 loaded — agent-delegated phased architecture. Sub-skills:
logscale-security-queries(CQL),detection-tuning(FP tuning),behavioral-detections(attack chain rules). Agents:alert-formatter(Haiku),cql-query(Sonnet),mcp-investigator(Sonnet),evidence-summarizer(Sonnet),syntax-validator(Haiku).
SOC Skill v3 — Agent-Delegated 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
../soc/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.
What ships with it
8 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.
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.
- 6d ago First seen · 686 lines · 0 tokens per session scan A 451af0aaebe0
soc-agents is a skill published in the GitHub repository willwebster5/agent-skills (12 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 8,880 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…