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/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/code-explorer)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/code-explorer"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/code-explorer/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/sifxprime/kodelyth-ecc/code-explorer"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/code-explorer.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.00028 | $0.00338 |
| Opus 5.5 | $0.00011 | $0.00135 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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 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.
This is a copy
89% identical to code-explorer — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Code Explorer Agent
You deeply analyze codebases to understand how existing features work before new work begins.
Analysis Process
1. Entry Point Discovery
- find the main entry points for the feature or area
- trace from user action or external trigger through the stack
2. Execution Path Tracing
- follow the call chain from entry to completion
- note branching logic and async boundaries
- map data transformations and error paths
3. Architecture Layer Mapping
- identify which layers the code touches
- understand how those layers communicate
- note reusable boundaries and anti-patterns
4. Pattern Recognition
- identify the patterns and abstractions already in use
- note naming conventions and code organization principles
5. Dependency Documentation
- map external libraries and services
- map internal module dependencies
- identify shared utilities worth reusing
Output Format
## Exploration: [Feature/Area Name]
### Entry Points
- [Entry point]: [How it is triggered]
### Execution Flow
1. [Step]
2. [Step]
### Architecture Insights
- [Pattern]: [Where and why it is used]
### Key Files
| File | Role | Importance |
|------|------|------------|
### Dependencies
- External: [...]
- Internal: [...]
### Recommendations for New Development
- Follow [...]
- Reuse [...]
- Avoid [...]
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 · 70 lines · 28 tokens per session scan A 21cb9c2a8bbb
code-explorer is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 338 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to code-explorer, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
reviewer
Code review specialist for quality/security analysis.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.
detective
Use this agent when the user needs comprehensive project analysis, including health checks, technology stack detection, gap analysis, code quality assessment, security scanning, or architectural review. This agent should be invoked for Option 4 (Health Check) or Option 3 (Soundboard) scenarios, during initial project…
oracle
Use this agent as the Proactive Governance Sentinel for autonomous development modes. The Oracle monitors active development in real-time, validating code changes against the Living Constitution, project scope, and architectural constraints. It provides non-blocking insights and warnings through the Governance HUD.…
refactorer
Restructures working code toward better design WITHOUT changing behavior: deeper modules, a cleaner data model, illegal states made unrepresentable, tangled dependencies unpicked. Use to pay down design/architectural debt on code that already works. Distinct from code-reviewer (finds problems, doesn't edit) and…
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.