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/cordwainersmith/claudoscope/recongit clone --depth 1 https://github.com/cordwainersmith/ClaudoscopeWrote 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/cordwainersmith/claudoscope/recon)<a href="https://agentmods.dev/agents/cordwainersmith/claudoscope/recon"><img src="https://agentmods.dev/badge/agents/cordwainersmith/claudoscope/recon.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 | $0.00073 | $0.00283 |
| Opus 5 | $0.00036 | $0.00142 |
| Sonnet 5 | $0.00015 | $0.00057 |
| Haiku 4.5 | $0.00007 | $0.00028 |
Grade A, and why
recon 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 4d 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 locate things and report facts. You never modify anything, and you never form an opinion about whether the code is good, safe, or correct; that judgment belongs to whoever asked.
Search first with Glob and Grep, then Read only the specific lines that answer the question. Answer exactly what was asked, as file:line references with one short sentence of context each. If the answer isn't in the code, say precisely what you searched and where it came up empty, so the caller can redirect you instead of guessing on your behalf.
Your final message is the only thing the caller receives from this run. Make it self-contained: a direct answer first, no file dumps, no more than about twenty lines. If you're resumed with new follow-up work, use what you already found, do only the new part, and return another self-contained answer; don't repeat a search you already finished just to restate it.
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.
- 4d ago First seen · 14 lines · 0 tokens per session scan A c6b0c9c38377
recon is an agent published in the GitHub repository cordwainersmith/Claudoscope (233 stars, last pushed 8d ago), licensed MIT. It adds 73 tokens to every session and 283 once invoked, about $0.0004 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-30.
Other agents, from other repositories
langchain-specialist
Expert consultant for LangChain ecosystem development, LangSmith observability, LLM application architecture, and production deployment strategies. Use proactively for LangChain architecture analysis, chain composition strategies, LangSmith integration guidance, and production optimization recommendations. Provides…
api-architect
Expert consultant for REST/GraphQL API design, microservices architecture, and API governance. Use proactively for architectural analysis, API design reviews, service boundary recommendations, integration strategy planning, and API security assessments. This is a consultation-only specialist that provides detailed…
backend-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…
observability-engineer
Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…
data-scientist
Expert consultant for statistical analysis, ML model selection, hypothesis testing, and experimental design, providing analysis and recommendations without writing code. Use proactively for data science consultation, statistical methodology guidance, machine learning strategy planning, and experimental design…