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 catlog22/Claude-Code-Workflow --skill investigategit clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWrote 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/catlog22/claude-code-workflow/investigate)<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/investigate"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/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.
<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/investigate"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/investigate.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.00036 | $0.01024 |
| Opus 5.5 | $0.00014 | $0.00410 |
| Sonnet 5.5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00102 |
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 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate
Systematic debugging skill that enforces the Iron Law: never fix without a confirmed root cause. Produces a structured debug report with full evidence chain, minimal fix, and regression test.
Iron Law Principle
No fix without confirmed root cause. Every investigation follows a strict evidence chain:
- Reproduce the bug with concrete evidence
- Analyze patterns to assess scope
- Form and test hypotheses (max 3 strikes)
- Implement minimal fix ONLY after root cause is confirmed
- Verify fix and generate structured report
Violation of the Iron Law (skipping to Phase 4 without Phase 3 confirmation) is prohibited.
Key Design Principles
- Evidence-First: Collect before theorizing. Logs, stack traces, and reproduction steps are mandatory inputs.
- Minimal Fix: Change only what is necessary. Refactoring is not debugging.
- 3-Strike Escalation: If 3 consecutive hypothesis tests fail, STOP and escalate with a diagnostic dump.
- Regression Coverage: Every fix must include a test that fails without the fix and passes with it.
- Structured Output: All findings are recorded in machine-readable JSON for future reference.
Execution Flow
Phase 1: Root Cause Investigation
Reproduce bug, collect evidence (errors, logs, traces)
Use ccw cli --tool gemini --mode analysis for initial diagnosis
Output: investigation-report.json
|
v
Phase 2: Pattern Analysis
Search codebase for similar patterns (same error, module, antipattern)
Assess scope: isolated vs systemic
Output: pattern-analysis section in report
|
v
Phase 3: Hypothesis Testing
Form max 3 hypotheses from evidence
Test each with minimal read-only probes
3-strike rule: STOP and escalate on 3 consecutive failures
Output: confirmed root cause with evidence chain
|
v
Phase 4: Implementation [GATE: requires Phase 3 confirmed root cause]
Implement minimal fix
Add regression test
Verify fix resolves reproduction case
|
v
Phase 5: Verification & Report
Run full test suite
Check for regressions
Generate structured debug report to .workflow/.debug/
What ships with it
7 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.
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 · 111 lines · 36 tokens per session scan A edb9d9a3f881
investigate is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,124 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,024 once invoked, about $0.0001 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-03.
Other skills, from other repositories
test-fix
Automatically invoke when any test run produces failures: FAIL output, test errors, or assertion failures in unit or E2E suites. Do NOT wait for the user to ask. Hard limit of 3 fix attempts per failure, then stops and escalates. Trigger on: "tests are failing", "fix the tests", "tests are broken".
ciel-root-cause-debugger
CIEL's framework for systematic error tracing, log analysis, and empirical bug fixing.
debugging-livekit-agents
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
dart-downstream-fix
DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo.
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.