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/unitoneai/securityskills/soc-analystnpx skills add UnitOneAI/SecuritySkills --skill soc-analystgit clone --depth 1 https://github.com/UnitOneAI/SecuritySkillsWrote 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/unitoneai/securityskills/soc-analyst)<a href="https://agentmods.dev/skills/unitoneai/securityskills/soc-analyst"><img src="https://agentmods.dev/badge/skills/unitoneai/securityskills/soc-analyst.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.00078 | $0.03997 |
| Opus 5 | $0.00039 | $0.01998 |
| Sonnet 5 | $0.00016 | $0.00799 |
| Haiku 4.5 | $0.00008 | $0.00400 |
Grade A, and why
soc-analyst 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOC Analyst Role Bundle (Tier 1-3)
A structured operations guide for security operations center analysts across all tiers. This bundle replaces reactive, ad-hoc alert handling with repeatable engagement patterns that produce consistent triage decisions, accurate incident timelines, and detection improvements that feed back into the monitoring pipeline.
When to Use
Invoke this role bundle when any of the following conditions are true:
- Alert triage required. A SIEM or detection tool has fired an alert and an analyst needs a structured workflow to determine whether it is a true positive, false positive, or requires escalation.
- Threat hunting engagement. The team wants to proactively search for adversary activity that existing detections are not catching, based on threat intelligence or hypotheses derived from the ATT&CK framework.
- Active incident investigation. A confirmed incident is in progress or recently occurred and the SOC needs to build a timeline, identify scope, contain the threat, and produce a post-incident report.
- Detection gap identified. Existing detection rules are producing too many false positives, missing known attack techniques, or a recent incident revealed a blind spot in monitoring coverage.
If the ask is a single tactical task (e.g., "write a Sigma rule for Kerberoasting"), use the individual skill directly. This bundle is for operational workflows that span multiple skills.
Skills: All skills referenced in this bundle are available: cve-triage, threat-modeling, secure-code-review, alert-triage, log-analysis, detection-engineering, siem-rules, ir-playbook, containment, forensics-checklist, post-incident-review.
Engagement Types
Each engagement type defines a skill sequence. Run the skills in order — each one produces outputs consumed by the next.
1. Alert Triage
Trigger: New alert from SIEM, EDR, or detection pipeline that requires analyst disposition.
Skill sequence:
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 · 362 lines · 78 tokens per session scan A 61520dc1bf60
soc-analyst is a skill published in the GitHub repository UnitOneAI/SecuritySkills (59 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 3,997 once invoked, about $0.0004 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
analyzing-dns-logs-for-exfiltration
Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
cis-aws-foundations-4.1
Ensure CloudTrail is enabled in all regions.
building-soc-escalation-matrix
Build a structured SOC escalation matrix defining severity tiers, response SLAs, escalation paths, and notification procedures for security incidents.
cis-aws-foundations-2.1.3
Ensure Organizations management account is not used for workloads.
cis-aws-foundations-2.12
Ensure access keys are rotated every 90 days or less.