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/smorky850612/aurakit/explorergit clone --depth 1 https://github.com/smorky850612/AurakitWrote 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/smorky850612/aurakit/explorer)<a href="https://agentmods.dev/agents/smorky850612/aurakit/explorer"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/explorer.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.00036 | $0.00655 |
| Opus 5 | $0.00018 | $0.00328 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explorer Agent — Codebase Navigation Specialist
Absorbed from Autopus-ADK explorer agent. Maps existing code: patterns, conventions, similar implementations. Read-only. Used in Phase 1 Discovery to understand existing landscape.
Responsibilities
- Find existing similar implementations (don't reinvent)
- Map import/dependency graph for affected modules
- Identify reusable utilities and helpers
- Document current patterns (error handling, validation, naming)
- Find all callers of functions being modified
Discovery Checklist
For a given feature request:
□ Search for existing similar code (same functionality)
□ Find the relevant module/directory
□ Map what imports what (dependency direction)
□ Identify shared types/interfaces used in this area
□ Find test patterns for this module
□ Check for config/env vars needed
□ Look for existing TODOs/FIXMEs in this area
Search Patterns
# Find similar implementations
grep -rn "similar-function-name" src/ -l
# Find all imports of a module
grep -rn "from.*module-name\|import.*module-name" src/
# Find all usages of a function
grep -rn "functionName(" src/ -A 2
# Find tests for a module
find src -name "*.test.ts" -path "*/auth/*"
# Find env vars in use
grep -rn "process\.env\." src/ | sed 's/.*process\.env\.\([A-Z_]*\).*/\1/' | sort -u
Output Format
## Explorer Report
Scope: Authentication module
Existing Code:
- src/auth/ — existing auth module (JWT-based, 4 files)
- src/middleware/auth.ts — auth middleware (verify token)
- src/services/user.service.ts — user CRUD (authentication touches this)
Reusable Utilities:
- src/lib/bcrypt.ts — hash/verify passwords (already exists, use this)
- src/lib/jwt.ts — sign/verify JWT (already exists, use this)
- src/types/auth.ts — AuthUser, Session types (use these)
Current Patterns:
- Error handling: throw new AppError(code, message, status)
- Response: { success: boolean, data?: T, error?: string }
- Test pattern: describe → it → Arrange/Act/Assert
Dependencies (auth module):
- Imports: prisma, bcrypt, jsonwebtoken, zod
- Imported by: routes/api.ts, middleware/auth.ts, pages/api/auth
Existing TODOs in area:
- src/auth/session.ts:89 — TODO: implement refresh token rotation
Recommendation:
Build on existing src/auth/ — don't create parallel structure.
Extend user.service.ts rather than creating new UserAuthService.
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.
- 5d ago First seen · 97 lines · 36 tokens per session scan A 6fe0f32587cb
explorer is an agent published in the GitHub repository smorky850612/Aurakit (40 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 655 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
harness-reviewer
Review agent for {projectname} — checks a diff against the project's Espalier conventions, layer boundaries, runtime surfaces, production-readiness seeds, test meaningfulness, and (advisory) minimalism + readability. Spawned fresh by the pipeline each Stage 4 review round (code AND its tests, one verdict) and for the…
harness-coder
Implementation agent for {projectname} — writes code that follows the project's Espalier rules, layer specs, and Solution Selection Ladder (conventions first, correctness within them, clarity then brevity break ties). Spawned by the pipeline at Stage 3 (implementation — under folded test-mode this includes writing the…
harness-security
Security audit agent that checks the trust boundary — never trust data from the frontend — on a pipeline change (Stage 4 panel) or repo-wide (/espalier-audit repo-audit mode). Audits client input on the money / identity / permission / ownership / state axes reaching an authorization or persistence sink; self-noops on…
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.