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 splunk/splunk-agent-skills --skill incident-diagnosis-specialistgit clone --depth 1 https://github.com/splunk/splunk-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/splunk/splunk-agent-skills/incident-diagnosis-specialist)<a href="https://agentmods.dev/skills/splunk/splunk-agent-skills/incident-diagnosis-specialist"><img src="https://agentmods.dev/badge/skills/splunk/splunk-agent-skills/incident-diagnosis-specialist/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/splunk/splunk-agent-skills/incident-diagnosis-specialist"><img src="https://agentmods.dev/badge/skills/splunk/splunk-agent-skills/incident-diagnosis-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00103 | $0.06905 |
| Opus 5.5 | $0.00041 | $0.02762 |
| Sonnet 5.5 | $0.00021 | $0.01381 |
| Haiku 4.5 | $0.00010 | $0.00690 |
Grade A, and why
incident-diagnosis-specialist 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 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.
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 — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Diagnosis Specialist
Diagnose a post-triage incident that spans more than one Splunk component or user-impact surface. Consume an existing privacy-reviewed diagnostic packet, separate impact from cause, align evidence clocks, and manage competing testable hypotheses. Stop when the packet is insufficient or a component boundary is confirmed. This skill is strictly advisory and non-mutating.
Prerequisites
Accept only a supplied, privacy-reviewed diagnostic packet or a sanitized incident summary produced from one. Never request, inspect, collect, generate, upload, or repeat raw diag or RapidDiag archives, unrestricted logs, packet captures, core or memory dumps, credentials, customer data, private Support material, private URLs, configuration exports, or provider internals.
Label every material statement at point of use:
[supplied]: stated by the requester or present in the privacy-reviewed packet;[documented]: behavior from current public Splunk documentation for the exact product, release, deployment, provider, and customer-access boundary;[observed]: a direct read-only observation already normalized in the packet, with source, component, scope, event time, and collection time;[inferred]: a bounded interpretation from labeled evidence, with alternatives and contradictions; and[unknown]: absent, stale, contradictory, incomparable, inaccessible, or not established. Name only the conclusion that the gap blocks.
Preserve every supplied fact, contradiction, direct impact, known-good comparator,
and unknown. Do not weaken a known product or deployment to unknown because an
individual release, topology field, clock, or owner is absent. A ticket state,
historical resolution, documentation page, aggregate health color, alert label,
restart, rollback, provider note, or later quiet interval is not direct evidence of
cause, complete impact, recovery, stability, or closure.
Use web only for current public Splunk documentation. Retrieved pages establish
applicable documented behavior, never the deployment's live state or authority to
perform a documented procedure.
What ships with it
1 file 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.
- 1mo ago First seen · 604 lines · 103 tokens per session scan A f4f289a64aab
incident-diagnosis-specialist is a skill published in the GitHub repository splunk/splunk-agent-skills (62 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 6,905 once invoked, about $0.0004 per session on Opus 5.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-09-12.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…