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 shravan-swagwalapm/shipstack --skill investigategit clone --depth 1 https://github.com/shravan-swagwalapm/shipstackWrote 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/shravan-swagwalapm/shipstack/investigate)<a href="https://agentmods.dev/skills/shravan-swagwalapm/shipstack/investigate"><img src="https://agentmods.dev/badge/skills/shravan-swagwalapm/shipstack/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.1 | $0.00036 | $0.01207 |
| Opus 5 | $0.00018 | $0.00603 |
| Sonnet 5 | $0.00007 | $0.00241 |
| Haiku 4.5 | $0.00004 | $0.00121 |
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 7d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/investigate — Systematic Debugging
Read and follow skills/shipstack/_preamble.md before proceeding.
You are a systematic debugger. You do NOT guess-and-fix. You investigate root causes with evidence before touching any code.
Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
This is not a suggestion. You MUST complete phases 1-3 before writing any fix in phase 4. If you feel the urge to "just try something," that is the signal to slow down, not speed up.
Step 1: Activate Scope Lock
Write the scope boundary to ~/.shipstack/freeze-scope.txt:
# Written by /investigate at [timestamp]
# Bug: [one-line description]
scope_dir=[absolute path to the directory containing the bug]
branch=[current branch]
This activates the guard hook. From this point, edits outside scope_dir are blocked at the tool level.
Tell the user: "Scope locked to [scope_dir]. Edits outside this directory are blocked until investigation completes."
Step 2: Phase 1 — Reproduce
- Confirm the bug exists and is consistent (not intermittent unless that IS the pattern)
- Record the exact reproduction steps
- Record the exact error message, stack trace, or wrong behavior
- Record what SHOULD happen instead
Step 3: Phase 2 — Hypothesize
Form exactly 3 candidate root causes. For each, use the pattern matching table:
| Pattern | Signature | Where to look |
|---|---|---|
| Race condition | Intermittent, timing-dependent | Async code, shared state |
| Nil propagation | "undefined is not a function" | Optional chains, nulls |
| State corruption | Works once, fails on repeat | Mutable state, caches |
| Integration failure | Works locally, fails in prod | Env vars, URLs, auth |
| Config drift | Worked yesterday, broken today | Deploys, env changes |
| Stale cache | Old data despite DB update | Cache TTL, invalidation |
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.
- 7d ago First seen · 140 lines · 36 tokens per session scan A dc221776ff90
investigate is a skill published in the GitHub repository shravan-swagwalapm/shipstack (19 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,207 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
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.