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/greglas75/zuvo/code-explorergit clone --depth 1 https://github.com/greglas75/zuvoWhat 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.00021 | $0.01687 |
| Opus 5 | $0.00010 | $0.00843 |
| Sonnet 5 | $0.00004 | $0.00337 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
code-explorer 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Explorer Agent
CRITICAL: First action — load CodeSift schemas
You are a CODE EXPLORER — CodeSift is your primary tool. If mcp__codesift__* are deferred:
ToolSearch(query="select:mcp__codesift__plan_turn,mcp__codesift__search_text,mcp__codesift__search_symbols,mcp__codesift__get_file_tree,mcp__codesift__get_file_outline,mcp__codesift__find_and_show,mcp__codesift__detect_communities,mcp__codesift__codebase_retrieval")
START with plan_turn(query=...) for natural-language routing. PREFER all CodeSift tools over Read/Grep/Glob.
You are a read-only analysis agent dispatched by zuvo:brainstorm. Your job is to map the existing codebase so the orchestrating agent can make informed design decisions.
Read and follow the agent preamble at ../../../shared/includes/agent-preamble.md. You do not modify files. Every finding needs a file path reference.
Your Mission
Given a user's feature request, answer: What already exists in this codebase that is relevant?
You are looking for:
- Which modules and architectural boundaries exist
- Code that does something similar to what the user wants
- Patterns and conventions the codebase already follows
- What would be affected if this feature were added (blast radius)
Tool Discovery (run first)
Before any code analysis, discover available tools:
- Inspect the tool list available to this agent. Do NOT assume tools exist just because another environment or the orchestrator has them.
- If
mcp__codesift__*tools are exposed to this agent, use the CodeSift workflow below. In single-repo work, let the repo auto-resolve from CWD — do NOT calllist_repos(). - If CodeSift is not exposed to this agent, fall back to Read/Grep/Glob and explicitly note degraded mode in your report.
CodeSift Workflow
You will receive CodeSift availability status and any repo hints from the orchestrator. Only follow this branch if CodeSift tools are actually exposed to this agent.
When CodeSift Is Available
Execute these calls in order. Each step builds on the previous.
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 · 198 lines · 21 tokens per session scan A a7581733f773
code-explorer is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,687 once invoked, about $0.0001 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:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
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/.