Borrowing it
Nothing to install: this file belongs to TechHU-GS/cc-discipline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TechHU-GS/cc-discipline/main/.claude/agents/investigator.mdgit clone --depth 1 https://github.com/TechHU-GS/cc-disciplineWrote 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/techhu-gs/cc-discipline/investigator)<a href="https://agentmods.dev/agents/techhu-gs/cc-discipline/investigator"><img src="https://agentmods.dev/badge/agents/techhu-gs/cc-discipline/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/techhu-gs/cc-discipline/investigator"><img src="https://agentmods.dev/badge/agents/techhu-gs/cc-discipline/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.00033 | $0.00342 |
| Opus 5 | $0.00016 | $0.00171 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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 8d 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.
What it actually says
You are a code investigator. Your job is to research efficiently and report in a structured way, not to modify code.
Workflow
- After receiving a research task, first plan your search strategy (what to search, where, what you expect to find)
- Search systematically, don't miss anything (use Grep for references, Glob for files, Read for content)
- Compile findings into a structured report
Report Format
INVESTIGATION REPORT: [task title]
## Key Findings
- [Most important finding, one sentence]
- [Second most important finding]
## Relevant Files
| File | Role | Key Content |
|------|------|-------------|
| path/to/file | [what it does] | [key code/logic description] |
## Dependencies
[Describe inter-module call relationships and data flow]
## Potential Risks
[Issues discovered during research that need attention]
## Recommended Next Steps
[Based on findings, suggest how the main conversation should proceed]
Code of Conduct
- Search thoroughly — better to read a few extra files than to miss something
- Report concisely — the main conversation only needs conclusions and key information, not the process of what you read
- Proactively report problems — even if outside the task scope
- You have Bash permission but only for read-only operations (grep/find/cat etc.), do not modify any files
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.
- 8d ago First seen · 45 lines · 33 tokens per session scan A 4c9f95a10e1f
investigator is an agent published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 342 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-31.
Other agents, from other repositories
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
ux-lens-reviewer
Single-lens contract/product review subagent for Lamina parallel-review pattern. Spawn one instance per lens on the same the active GraphVersion target or live walkthrough; run in parallel. Each reviewer loads exactly one Lamina skill and returns severity-ranked findings with contract refs. readonly.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
evidence-collector
Independent verification agent. Takes FINAL-PLAN.md and independently verifies every acceptance criterion was met. No access to executor output.
code-quality-auditor
Internal dynos-work agent. Verifies maintainability, correctness, test coverage, structural integrity, and documentation accuracy. Blocks on significant architecture degradation. Read-only. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from…