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/ramdhavepreetam/nervapack/exploregit clone --depth 1 https://github.com/ramdhavepreetam/NervaPackWrote 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/ramdhavepreetam/nervapack/explore)<a href="https://agentmods.dev/commands/ramdhavepreetam/nervapack/explore"><img src="https://agentmods.dev/badge/commands/ramdhavepreetam/nervapack/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.00000 | $0.00760 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
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 3d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nervapack explore
Extract and visualize the N-hop neighbourhood of a specific file, class, or function.
Synopsis
nervapack explore TARGET [OPTIONS]
Description
explore is visualize scoped to a single entity. You give it a file path, class name, or function name and it:
- Finds all graph nodes that match the target string (by file path, node name, or node ID).
- Runs a multi-source BFS to N hops from those seed nodes.
- Generates an enhanced HTML visualization of just that subgraph — with search and path finder enabled.
Use explore when you want to understand one module's relationships without the noise of the full graph.
Arguments and Options
| Argument / Option | Default | Description |
|---|---|---|
TARGET |
(required) | File path, class name, function name, or partial string to match |
--hops N / -h N |
2 |
Number of BFS hops from the matched nodes |
--output PATH |
.nervapack/explore_{target}.html |
Where to save the HTML file |
--no-browser |
off | Generate without opening the browser |
Examples
Explore a class by name
nervapack explore GraphBuilder --hops 2
Explore a file
nervapack explore src/graph/builder.py --hops 1
Partial name match (all nodes containing "store")
nervapack explore store --hops 1
Save to a custom path
nervapack explore AuthMiddleware --output ~/graphs/auth.html
Output
Exploring neighborhood of 'GraphBuilder' (hops=2)...
Found 3 matching nodes:
- class:src/nervapack/graph/builder.py:GraphBuilder
- function:src/nervapack/graph/builder.py:build_from_entities
- function:src/nervapack/graph/builder.py:save_graph
Extracting 2-hop neighborhood...
Subgraph: 47 nodes, 83 edges
Visualization saved: .nervapack/explore_GraphBuilder.html
Opened in browser.
Use cases
| Goal | Command |
|---|---|
| Understand a class before refactoring | nervapack explore MyClass --hops 2 |
| Check who calls a function | nervapack explore my_function --hops 1 |
| See what a file imports and exports | nervapack explore src/foo.py --hops 1 |
| Onboard to a module quickly | nervapack explore src/auth/ --hops 2 |
| Pre-review impact check | nervapack explore ChangedClass --hops 2 |
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.
- 3d ago First seen · 108 lines · 0 tokens per session scan A 3a398da65d00
explore is a command published in the GitHub repository ramdhavepreetam/NervaPack (1 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 760 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.