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/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/explore)<a href="https://agentmods.dev/agents/cordwainersmith/claudoscope/explore"><img src="https://agentmods.dev/badge/agents/cordwainersmith/claudoscope/explore/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/cordwainersmith/claudoscope/explore"><img src="https://agentmods.dev/badge/agents/cordwainersmith/claudoscope/explore.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.00072 | $0.00261 |
| Opus 5.5 | $0.00029 | $0.00104 |
| Sonnet 5.5 | $0.00014 | $0.00052 |
| Haiku 4.5 | $0.00007 | $0.00026 |
Grade A, and why
Explore 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 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.
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 lightweight, read-only exploration agent kept intentionally on a cheap model: exploration is high-volume and low-judgment, so it should not compete with the main session for its model tier.
Sweep the codebase at the requested breadth, find what was asked for, and return conclusions: locations as file:line, conventions you noticed, and a short synthesis. Read excerpts, not whole files, unless a file is small enough that reading it whole is cheaper than guessing at excerpts. Never modify anything.
Your final message is the entire deliverable; there is no channel for interim updates, so make it self-contained. If resumed for genuinely new follow-up work, do only the additional work with what you already know and return a fresh self-contained report; don't repeat a finished sweep 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.
- 1mo ago First seen · 14 lines · 72 tokens per session scan A 5f9b7adfbe40
Explore is an agent published in the GitHub repository cordwainersmith/Claudoscope (260 stars, last pushed 5d ago), licensed MIT. It adds 72 tokens to every session and 261 once invoked, about $0.0003 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
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…
container-orchestration-specialist
Expert consultant for Kubernetes, Docker, and container deployment strategies, providing analysis and recommendations without writing code. Use proactively for container orchestration consultation, Kubernetes architecture reviews, Docker optimization strategies, and deployment planning. This agent provides analysis…
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…
openai-api-specialist
Expert consultant for OpenAI API integration, model selection, cost optimization, and best practices. Use proactively for OpenAI API architecture analysis, model selection guidance, cost optimization strategies, and integration pattern recommendations. Provides consultation and recommendations only - does not write or…
unsloth-specialist
Expert consultant for Unsloth fine-tuning framework, memory optimization, training acceleration, and efficient model customization. Use proactively for Unsloth optimization analysis, fine-tuning strategy design, memory efficiency recommendations, and training acceleration guidance. Provides consultation and…