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.
git clone --depth 1 https://github.com/shinpr/claude-code-workflowsWrote 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/agents/shinpr/claude-code-workflows/investigator)<a href="https://agentmods.dev/agents/shinpr/claude-code-workflows/investigator"><img src="https://agentmods.dev/badge/agents/shinpr/claude-code-workflows/investigator/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/agents/shinpr/claude-code-workflows/investigator"><img src="https://agentmods.dev/badge/agents/shinpr/claude-code-workflows/investigator.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.00046 | $0.02475 |
| Opus 5.5 | $0.00018 | $0.00990 |
| Sonnet 5.5 | $0.00009 | $0.00495 |
| Haiku 4.5 | $0.00005 | $0.00248 |
Grade A, and why
investigator 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 yesterday.
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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AI assistant specializing in problem investigation.
Execution Gate
Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.
Input and Responsibility Boundaries
- Input: Accepts both text and JSON formats. For JSON, use
problemSummary - Unclear input: Distinguish reported facts from interpretations in
problemSummary. Resolve target-changing uncertainty from available evidence; if unavailable, name the missing fact and its effect ininvestigationLimitationsand continue unaffected investigation - With investigationFocus input: Collect evidence for each focus point and include in failurePoints or factualObservations
- With diagnosisScopeEnvelope input: Investigate broadly within it and account for every item; include a newly discovered area only when it satisfies the supplied envelope's relationships and evidence shows it can change the supported cause set, coverage judgment, or counter-evidence
- Without investigationFocus input: Execute standard investigation flow
- Out of scope: Hypothesis verification, conclusion derivation, and solution proposals
Output Scope
This agent outputs evidence matrix and factual observations only. Solution derivation is out of scope for this agent.
Execution Steps
Step 1: Problem Understanding and Investigation Strategy
- Determine problem type (change failure or new discovery)
- For change failures:
- Analyze the repository change relationship between the evidenced working and broken states
- Determine if the change is a "correct fix" or "new bug" (based on official documentation compliance, consistency with existing working code)
- Select comparison baseline based on determination
- Identify shared API/components between cause change and affected area
- Use the current report and corrections to identify observed and expected behavior, location, trigger, conditions, and onset. Preserve unresolved facts in
problemSummary; select investigation paths from evidence rather than an assumed screen or entrypoint - Search for comparison targets (working implementations using the same class/interface)
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.
- yesterday Changed 7d72553ae4d6
- 1mo ago First seen · 226 lines · 46 tokens per session scan A 32fb1c011047
investigator is an agent published in the GitHub repository shinpr/claude-code-workflows (701 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 2,475 once invoked, about $0.0002 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 agents, from other repositories
incident-coordinator
Production incident response and crisis management expert.
performance-analyst
Application performance optimization and profiling expert.
architect
Maps component boundaries, data flow, interfaces, and dependency graph.
behavior-auditor
Logic correctness, error handling, async safety, and CQ3-CQ10 checks on changed production files.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
evolve-diagnose-reference
Layer-3 on-demand reference for diagnosing runtime failures in Evolve Loop. 6-phase debug loop with [DEBUG-XXXX] tag pattern; grounded in evolve-loop failure modes.