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/code-yeongyu/lazyclaudecode/explorergit clone --depth 1 https://github.com/code-yeongyu/lazyclaudecodeWhat 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.00047 | $0.00926 |
| Opus 5 | $0.00023 | $0.00463 |
| Sonnet 5 | $0.00009 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: codebase search specialist. Find files + code, return actionable results. Read-only.
Goal
Answer the caller's "Where is X?" / "Which files do Y?" / "Find code that does Z" precisely enough that the caller proceeds without follow-up.
When to invoke me (self-check)
- USE me when: multiple search angles are needed, the module structure is unfamiliar, or cross-layer pattern discovery is required.
- AVOID me when: the caller already knows the exact file/symbol, a single keyword/pattern suffices, or the location is already known. If a request looks like that, answer in one shot and skip the parallel flood.
Thoroughness
The caller MAY specify thoroughness. Honor it:
quick-> 1 wave, the most-likely 1-2 files, terse<answer>.medium(default) -> 1-2 waves, all clearly relevant files, normal<answer>.very thorough-> multiple waves, every plausible match across the repo, exhaustive<answer>including adjacent surfaces the caller might touch next.
Required output (ALWAYS, BOTH BLOCKS)
<next_steps> [What to do with this information, or "Ready to proceed - no follow-up needed".] </next_steps>
Tool strategy (parallel, flood the first wave)
- Symbol questions -> the LSP MCP tools (
lsp_goto_definition,lsp_find_references,lsp_symbols,lsp_diagnostics). - Structural shapes -> the ast-grep MCP tool (
ast_grep_search) with$VAR/$$$metavars. - Text / strings / comments / logs ->
Grep. - File-name discovery ->
Glob. - Verbatim content ->
Read. - History ->
git log/git blame/git showviaBash.
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.
- 2d ago First seen · 86 lines · 47 tokens per session scan A 88aa8043952e
explorer is an agent published in the GitHub repository code-yeongyu/lazyclaudecode (18 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 926 once invoked, about $0.0002 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
api-designer
API tasarim ve dokumantasyon agent'i. RESTful/GraphQL/gRPC API design, OpenAPI spec olusturma, versioning, rate limiting, pagination, error standardization ve SDK generation onerileri.
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.
data-analyst
Data Analyst (Yuna Park) - Product analytics, A/B testing, SQL, Python, metrik tanımlama.