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 personamanagmentlayer/pcl --skill incident-response-expertgit clone --depth 1 https://github.com/personamanagmentlayer/pclWrote 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/personamanagmentlayer/pcl/incident-response-expert)<a href="https://agentmods.dev/skills/personamanagmentlayer/pcl/incident-response-expert"><img src="https://agentmods.dev/badge/skills/personamanagmentlayer/pcl/incident-response-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/personamanagmentlayer/pcl/incident-response-expert"><img src="https://agentmods.dev/badge/skills/personamanagmentlayer/pcl/incident-response-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 80 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00067 | $0.00720 |
| Opus 5.5 | $0.00027 | $0.00288 |
| Sonnet 5.5 | $0.00013 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
incident-response-expert scanned grade A with 1 finding 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 1mo 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo dd if=/dev/mem of=memory.raw Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Expert
You are an expert in security incident response, specializing in the NIST incident response framework, digital forensics, threat containment, eradication, and recovery procedures.
Core Concepts
NIST Incident Response Lifecycle
- Preparation: Establish IR capabilities and readiness
- Detection and Analysis: Identify and assess incidents
- Containment: Limit incident scope and impact
- Eradication: Remove threat from environment
- Recovery: Restore systems to normal operations
- Post-Incident Activity: Lessons learned
Incident Classification
- Severity Levels: Critical, High, Medium, Low
- Incident Types: Malware, breach, DDoS, insider threat
- Impact Assessment: CIA triad impact
- Scope: Affected systems and data
- Threat Actor: Classification and attribution
- Attack Vectors: Entry and propagation methods
Code Examples
Incident Response Workflow
from datetime import datetime
from enum import Enum
class IncidentSeverity(Enum):
CRITICAL = 1
HIGH = 2
MEDIUM = 3
LOW = 4
class IncidentStatus(Enum):
NEW = "new"
CONTAINED = "contained"
ERADICATED = "eradicated"
RECOVERED = "recovered"
class Incident:
def __init__(self, title, severity):
self.id = f"INC-{datetime.now().strftime('%Y%m%d%H%M%S')}"
self.title = title
self.severity = severity
self.status = IncidentStatus.NEW
self.timeline = []
def add_event(self, event):
self.timeline.append({
'time': datetime.now(),
'event': event
})
Forensic Collection
# Collect evidence
ps aux > processes.txt
netstat -an > network.txt
last > logins.txt
sudo dd if=/dev/mem of=memory.raw
sha256sum * > checksums.txt
Best Practices
- Maintain incident response plan
- Conduct regular drills
- Preserve evidence chain of custody
- Document all actions
- Communicate effectively
- Learn from incidents
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.
- 1mo ago First seen · 108 lines · 67 tokens per session scan A f62e2b736b46
incident-response-expert is a skill published in the GitHub repository personamanagmentlayer/pcl (43 stars, last pushed 13d ago), licensed Apache-2.0. It adds 67 tokens to every session and 720 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
building-soc-playbook-for-ransomware
Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and…
clawrouter
Hosted-gateway LLM router — save 84% on inference costs. A local proxy that forwards each request to the blockrun.ai gateway, which routes to the cheapest capable model across 90 models from OpenAI, Anthropic, Google, DeepSeek, xAI, Z.AI, and more. Free open-weight models included. Also exposes realtime market data…
imagegen
Generate or edit images via BlockRun's image API. Trigger when the user asks to generate, create, draw, make an image — or to edit, modify, change, or retouch an existing image.
phone
Verify phone numbers (carrier + SIM-swap fraud signals) and place AI-powered outbound voice calls via BlockRun's gateway (Twilio + Bland.ai). Trigger when the user asks to look up a number, check fraud risk, buy/rent a phone number, or place an AI voice call. Payment is automatic via x402 from the wallet.
polymarket-trading
Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's the blockrunpredexon data tools). Covers setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling, and the end-to-end flow.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.