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 dandye/ai-runbooks --skill respond-phishinggit clone --depth 1 https://github.com/dandye/ai-runbooksWrote 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/dandye/ai-runbooks/respond-phishing)<a href="https://agentmods.dev/skills/dandye/ai-runbooks/respond-phishing"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/respond-phishing/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/dandye/ai-runbooks/respond-phishing"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/respond-phishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01599 |
| Opus 5 | $0.00024 | $0.00800 |
| Sonnet 5 | $0.00010 | $0.00320 |
| Haiku 4.5 | $0.00005 | $0.00160 |
Grade A, and why
respond-phishing 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 12d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phishing Incident Response Skill
Structured workflow for responding to reported phishing emails using the PICERL model.
Inputs
CASE_ID- SOAR case ID for the incidentALERT_GROUP_IDENTIFIERS- Alert group identifiers from SOARREPORTED_EMAIL_ARTIFACTS- Information about the email:- Email headers
- Email body
- Attached files (hashes)
- URLs in email
- Recipient user ID(s)
- Sender address/domain
Required Outputs
After completing each phase, you MUST report these outputs:
Identification Phase
| Output | Description |
|---|---|
PHISHING_URLS |
URLs extracted from email body |
PHISHING_IOCS |
Confirmed malicious indicators (URLs, domains, hashes) |
AFFECTED_USERS |
All users who received the email |
CLICKED_USERS |
Users who clicked/interacted with malicious content |
PHISHING_CATEGORY |
Type: credential phish, spear phishing, BEC, malware delivery |
Containment Phase
| Output | Description |
|---|---|
BLOCKED_IOCS |
IOCs blocked at email gateway/proxy/firewall |
CONTAINED_USERS |
User accounts with restrictions applied |
ISOLATED_ENDPOINTS |
Endpoints isolated due to suspicious activity |
Eradication Phase
| Output | Description |
|---|---|
DELETED_EMAILS |
Count of malicious emails removed from mailboxes |
QUARANTINED_EMAILS |
Emails moved to quarantine |
Recovery Phase
| Output | Description |
|---|---|
RESTORED_ACCOUNTS |
User accounts restored to normal access |
USER_NOTIFICATIONS |
Users notified of incident and required actions |
PICERL Phases
Phase 2: Identification
Step 2.1: Get Context & Check Duplicates
secops-soar.get_case_full_details(case_id=CASE_ID)
Use /check-duplicates.
Step 2.2: Analyze Email Artifacts
Extract from email:
- All URLs →
EXTRACTED_URLS - Sender domain/IP
- Attachment hashes →
EXTRACTED_HASHES - Reply-to addresses
- Header anomalies (SPF/DKIM failures)
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.
- 12d ago First seen · 258 lines · 48 tokens per session scan A dd8adbef8a8c
respond-phishing is a skill published in the GitHub repository dandye/ai-runbooks (124 stars, last pushed 27d ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,599 once invoked, about $0.0002 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…