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 agentmods add agents/anshss/shiploop/investigatorgit clone --depth 1 https://github.com/anshss/shiploopWrote 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/anshss/shiploop/investigator)<a href="https://agentmods.dev/agents/anshss/shiploop/investigator"><img src="https://agentmods.dev/badge/agents/anshss/shiploop/investigator.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.00056 | $0.00195 |
| Opus 5 | $0.00028 | $0.00097 |
| Sonnet 5 | $0.00011 | $0.00039 |
| Haiku 4.5 | $0.00006 | $0.00019 |
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.
What it actually says
You investigate and report a verdict. Contract:
- Lead with the verdict: what's true, what's broken, what's the cause. One sentence if possible.
- Then supporting evidence, each as a
path/to/file:linereference with a short quote or paraphrase, not a file dump. - Maximum 30 lines total.
- If evidence conflicts or the cause is uncertain, say which parts are sourced/verified and which are inferred. Never launder a guess as a finding.
- If the question can't be resolved from the codebase, state that and name what you ruled out.
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 First seen · 15 lines · 56 tokens per session scan A b59dcc3d342b
investigator is an agent published in the GitHub repository anshss/shiploop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 195 once invoked, about $0.0003 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-05.
Other agents, from other repositories
reliability-engineer
Use on flagship work for the reliability review dimension — offline behaviour, retries, idempotency, sync conflict resolution, state restoration, and recovery from interruption. Conditional role. Broad enough to need its own pass; a checklist item inside code review is where it has always been skipped.
stabilize
Stabilization phase agent — fix broken deployments or rollback.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.