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/leifericf/agentic-sdk/investigatenpx skills add leifericf/agentic-sdk --skill investigategit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/investigate)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/investigate"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/investigate.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.00015 | $0.00804 |
| Opus 5 | $0.00008 | $0.00402 |
| Sonnet 5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
investigate 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
investigate
Role: the ops entry point. Takes an incident (alerts, logs, a failing behavior, a report) to a root-cause analysis, a blameless review, and a follow-up plan ready to enter the backlog.
Prerequisites
At least one of: a log excerpt or alert payload, a time window and
environment, a reproduction, or an incident summary.
~/.agentic-sdk/<project>/project.edn and ~/.agentic-sdk/<project>/artifacts/ops/ exist (run
bootstrap-project first).
Procedure
- Triage the signals. Dispatch triage-logs with the smallest
useful packet: one alert or error, the timeframe, the environment.
It separates symptoms from operator signals, assesses impact,
checks recent changes, forms ranked hypotheses, and proposes
reversible mitigations. It writes
ops/<date>_triage_<slug>.md. Hold its one-line return. - Trace the root cause. Dispatch analyze-root-cause against the
triage artifact. It anchors on one precise failure mode, traces the
causal chain back from failure to trigger, runs the technical deep
dive (why tests and monitoring missed it), documents reproduction,
and defines preventative controls (each with type, what it prevents,
how to verify, owner). It writes
ops/<date>_rca_<slug>.md. Hold its one-line return. - Review the incident, blameless. Dispatch review-incident against
the triage and the RCA. It establishes impact and detection, builds
the timeline, documents the response, identifies contributing factors
across product, technical, data, operational, and process
dimensions, and defines action items (each with type: prevent,
detect, or mitigate; owner; due date). It writes
ops/<date>_incident_<slug>.md. Hold its one-line return. - Draft the follow-up plan. From the three returns, compose the
follow-up plan: the immediate fix (one fix-bug or implement-change
item), the hardening tasks (the preventative controls from the RCA),
the backlog items (the review's product or process action items),
and the verification plan (the test or drill that proves the control
works). Promote any architectural choice the investigation settles
to an ADR via record-decision. Resolve open questions in
open-questions.md. - Present the gate. Show the maintainer the triage, RCA, and incident review paths plus the follow-up plan. The follow-up plan is the one approval gate. On approval, fix items hand to fix-bug (a single bug) or implement-change (a slice); backlog items enter the backlog via the normal planning cycle.
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 · 72 lines · 15 tokens per session scan A 5532985dbe59
investigate is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 804 once invoked, about $0.0001 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-31.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…