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 sirkirby/unifi-mcp --skill incident-investigationgit clone --depth 1 https://github.com/sirkirby/unifi-mcpWrote 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/sirkirby/unifi-mcp/incident-investigation)<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/incident-investigation"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/incident-investigation/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/sirkirby/unifi-mcp/incident-investigation"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/incident-investigation.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.00077 | $0.05869 |
| Opus 5.5 | $0.00031 | $0.02348 |
| Sonnet 5.5 | $0.00015 | $0.01174 |
| Haiku 4.5 | $0.00008 | $0.00587 |
Grade A, and why
incident-investigation 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 14d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- incident-investigation — 100% identical, 441 lines differ
How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Device Incident Investigation
Investigate one Network device incident over one explicit window. Every claim in
the report cites evidence: records and per-source coverage returned by
the two incident evidence tools. Each tool returns a bounded view of its
evidence document (schema: "unifi-incident-evidence-view") that fits in one
tool result: every source's outcome, failure and coverage, plus the record
citations that fit (at most max_records_returned), with omitted records
counted and a cursor to read the rest. The local product servers are the whole
transport; nothing here needs the cloud worker or the relay.
Dependencies
Requires: network, protect Optional: worker
The investigation needs unifi_get_incident_evidence (Network) and
protect_get_incident_evidence (Protect). Discovery shows a tool is listed, not
that its controller is reachable or authorized; the evidence documents report
that per source.
- Protect not connected. Stop the canonical investigation and report Protect unavailable. Offer a Network-only investigation; with the user's consent, run the same workflow without the Protect call and label the report "Network-only: Protect unavailable, no camera context". A Network-only report never reaches complete coverage of the incident.
- Network not connected. Stop and report Network unavailable. There is no device evidence to investigate.
- Cloud worker. Not needed. Its location timeline, reached through a connected relay, collects the same evidence through these two tools and returns one combined document; this workflow calls the tools directly so each product's document and budgets stay separate. When you reach the product servers through the cloud worker, call the same two evidence tools.
Use the product setup skills for connection help; never ask for secrets.
Coverage and Limitations
Every report has a Coverage and Limitations section built from the evidence documents, never from memory or from record counts alone:
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.
- 14d ago Changed · +373 lines · +31 tokens per session f87aa2d5d5cd
- 15d ago Changed · +30 lines 888559c7106a
- 1mo ago First seen · 33 lines · 46 tokens per session scan A 5ac9db5f9a86
incident-investigation is a skill published in the GitHub repository sirkirby/unifi-mcp (955 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 5,869 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
memory-leak-debugging
Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.