agentmods.dev

mk:investigate

mk:investigate is a skill for Claude Code from ngocsangyem/MeowKit. It costs 116 tokens per session (1,748 once invoked), scanned A, original, MIT.

A structured debugging guide that investigates an error or bug and produces a diagnostic report before any code changes are made.

In plain words
What is it for?
Use it to investigate broken behaviour, troubleshoot errors, and prepare findings for a separate remediation step.
Why use it?
It helps prevent premature fixes by identifying and recording the underlying cause first.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool; built for gstack.

not rated 14repo 1mo ago A scan 116 tokens original MIT

Good fit Use it to investigate broken behaviour, troubleshoot errors, and prepare findings for a separate remediation step.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ngocsangyem/meowkit/investigate
View source ↗ ngocsangyem/MeowKit docs.meowkit.dev
Install

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.

Any agent
npx skills add ngocsangyem/MeowKit --skill investigate
Clone the repo
git clone --depth 1 https://github.com/ngocsangyem/MeowKit

Made for: Claude Code.

Wrote 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.

agentmods badge for mk:investigate

README.md
[![agentmods](https://agentmods.dev/badge/skills/ngocsangyem/meowkit/investigate/github.svg)](https://agentmods.dev/skills/ngocsangyem/meowkit/investigate)
Your own site
<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/investigate"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/investigate/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.

agentmods 80×15 button for mk:investigate

Your own site · 80×15
<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/investigate"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/investigate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,748 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00116 $0.01748
Opus 5 $0.00058 $0.00874
Sonnet 5 $0.00023 $0.00350
Haiku 4.5 $0.00012 $0.00175

Measured 8d ago against content hash 8415a453b80d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

mk: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 8d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (bin/check-freeze.sh, bin/check-report-path.sh, scripts/find-polluter.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/investigate/SKILL.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Systematic Investigation

Path convention: Commands below assume cwd is $CLAUDE_PROJECT_DIR (project root). Prefix paths with "$CLAUDE_PROJECT_DIR/" when invoking from subdirectories.

Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.

Skill wiring

  • Reads memory: canonical .meowkit/memory/fixes.json and architecture-decisions.json; fall back to matching generated Markdown views only when JSON is absent. See .claude/rules/memory-read-rules.md.
  • Writes: a diagnostic report only, under tasks/reports/**; the hook enforces this path. mk:fix owns remediation and any memory capture after a fix.

Plan-First Gate

Investigation precedes planning for bug fixes:

  1. Confirm root cause FIRST (Iron Law)
  2. After root cause confirmed, hand off to mk:fix. If the remedy affects more than two files, mk:fix requests an approved bug-fix plan using supported plan-creator syntax.

Skip: Investigation itself doesn't need a plan — it produces the input for planning.

When to Use

  • User reports errors, bugs, unexpected behavior
  • "debug this", "fix this bug", "why is this broken"
  • "investigate this error", "root cause analysis"
  • Troubleshooting why something stopped working

Process

  1. Run preamble — load references/preamble.md and execute the startup bash block
  2. Collect symptoms — read error messages, stack traces, reproduction steps
  3. Investigate root cause — load references/debugging-methodology.md and follow Phase 1-3. For recurring patterns or complex failures, load references/rca-method-selection.md for methodology selection. Load references/rca-anti-patterns.md to avoid common RCA mistakes.
  4. Check alternatives — test the strongest competing explanation before declaring a root cause.
  5. Write diagnostic report — save only to tasks/reports/{timestamp}-investigation-{slug}.md; include the required output contract below.
  6. Hand off — route confirmed defects to mk:fix, compile/build failures to mk:build-fix, and unresolved causes back to the user with explicit uncertainty.
  7. Run shared protocols — load references/shared-protocols.md for completion status + telemetry

Read the full file on GitHub · 145 lines

Files

What ships with it

13 files 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.

Changes

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.

  1. 8d ago First seen · 145 lines · 116 tokens per session scan A 8415a453b80d

Subscribe to this mod's changes

mk:investigate is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 1,748 once invoked, about $0.0006 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-09-03.

Claude CodeDebuggingaiai-agentsautomationclaudeclaude-skillsdebugfour-phaseinvestigateiron-lawroot-causesystematic-debugging
Related

Other skills, from other repositories

trace

Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…

jeremylongshore/tons-of-skills-marketplace · 84 tokens

audit

Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.

oliver-kriska/claude-elixir-phoenix · 35 tokens

investigate

Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.

oliver-kriska/claude-elixir-phoenix · 40 tokens

narrow-bare-rescue

Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.

oliver-kriska/claude-elixir-phoenix · 40 tokens

tidewave-integration

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

oliver-kriska/claude-elixir-phoenix · 38 tokens

verify

Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.

oliver-kriska/claude-elixir-phoenix · 33 tokens