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 commands/postrv/narsil-mcp/exploregit clone --depth 1 https://github.com/postrv/narsil-mcpWrote 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/commands/postrv/narsil-mcp/explore)<a href="https://agentmods.dev/commands/postrv/narsil-mcp/explore"><img src="https://agentmods.dev/badge/commands/postrv/narsil-mcp/explore.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.00007 | $0.00335 |
| Opus 5 | $0.00003 | $0.00168 |
| Sonnet 5 | $0.00001 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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 4d 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
Explore Codebase
Help the user understand the structure and organization of an unfamiliar codebase.
Workflow
Execute the following steps:
-
Identify repository: If $ARGUMENTS is provided, use it as the repo name. Otherwise, use
list_reposto show available repositories and ask which one to explore. -
Check capabilities: Use
get_index_statusto see which features are enabled (git, call-graph, etc.) -
Show structure: Use
get_project_structurewithmax_depth=3to show the directory tree -
Find main components:
- Use
find_symbolswithsymbol_type="class"to find main data structures - Use
find_symbolswithsymbol_type="function"andpattern="*main*"to find entry points
- Use
-
Understand dependencies: Use
get_import_graphto show how modules connect -
Check for issues: Use
find_circular_importsto identify potential architectural problems -
Optional graph manifest (only if
get_index_statusshows--graphenabled): Useget_ccg_manifestfor a compact AI-context-friendly summary of repository identity, symbol counts, and security posture. -
Summarize: Provide a clear summary of:
- Project structure and organization
- Key modules and their purposes
- Entry points
- Any architectural concerns (circular deps, etc.)
Arguments
Repository to explore: $ARGUMENTS
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.
- 4d ago First seen · 38 lines · 7 tokens per session scan A b16317ca0d2f
explore is a command published in the GitHub repository postrv/narsil-mcp (181 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 335 once invoked, about $0.0000 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 commands, from other repositories
localnest:recall
Recall relevant memories for the current task or query.
localnest:remember
Save a decision, fact, or learning to LocalNest memory.
localnest:prime
Get full task context — memories, entities, files, changes, and actions in one call.
localnest:fact
Add a structured fact to the knowledge graph.
localnest:ingest
Ingest a conversation file into memory and knowledge graph.
localnest:onboard
Run the guided first-run setup wizard that configures everything automatically.