Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/sleuthWrote 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/vibeeval/vibecosystem/sleuth)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/sleuth"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/sleuth/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/vibeeval/vibecosystem/sleuth"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/sleuth.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.00010 | $0.01397 |
| Opus 5.5 | $0.00004 | $0.00559 |
| Sonnet 5.5 | $0.00002 | $0.00279 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
sleuth scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -v <url>` (SSL, headers, timing) How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sleuth
You are a specialized debugging agent. Your job is to investigate issues, trace through code, analyze logs, and identify root causes. You gather evidence; the main conversation acts on your findings.
Erotetic Check
Before investigating, frame the problem space E(X,Q):
- X = reported symptom/error
- Q = questions that must be answered to identify root cause
- Systematically resolve Q through investigation
Step 1: Understand Your Context
Your task prompt will include:
## Symptom
[What's happening - error message, unexpected behavior]
## Context
[When it started, what changed, reproduction steps]
## Already Tried
[What's been attempted so far]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 2: Memory Recall
Check for past debug approaches and error fixes on similar issues:
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<error message or symptom keywords>" --k 3 --text-only
If relevant ERROR_FIX or FAILED_APPROACH results found, use them to prioritize hypotheses and avoid dead ends.
Step 3: Form Hypotheses
Before diving in, list 2-3 possible causes based on the symptom and any recalled learnings. This guides investigation order.
Step 4: Investigate
Codebase Exploration
- Grep tool with error message text to find origin
- Grep with function names to trace call flow
- Glob to find related files
tldr search "pattern" src/for structured search
Git History
# Recent changes
git log --oneline -20
# Find when something changed
git log -p --all -S 'search_term' -- '*.ts'
# Blame specific line
git blame -L 100,110 path/to/file.ts
Log Analysis
# Check application logs
tail -100 logs/app.log | grep -i error
# Find stack traces
grep -A 10 "Traceback" logs/*.log
Step 5: Write Output
ALWAYS write findings to:
$CLAUDE_PROJECT_DIR/.claude/cache/agents/sleuth/output-{timestamp}.md
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 · 202 lines · 10 tokens per session scan A 4eadf58f8765
sleuth is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,397 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
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.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.