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/visualizegit clone --depth 1 https://github.com/ramdhavepreetam/NervaPackWhat 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.01238 |
| Opus 5 | $0.00000 | $0.00619 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
visualize 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nervapack visualize
Render the knowledge graph as an interactive, standalone HTML file.
Synopsis
nervapack visualize [OPTIONS]
Description
visualize reads the graph from .nervapack/graph.graphml and generates a self-contained HTML file with no external dependencies — drag, zoom, search, and share it without any server.
Two rendering modes are available:
- Basic (default) — spring-force physics layout, hover tooltips, node colours by type.
- Enhanced (
--enhanced,--communities) — adds real-time search, shortest-path finder, and Louvain community detection.
Options
| Option | Default | Description |
|---|---|---|
--output PATH |
.nervapack/graph.html |
Where to save the HTML file |
--scope TARGET |
(none) | Only render the neighborhood around a file/name/node (e.g. a program name). Physics stays on for these small, readable views. |
--hops N |
2 |
Neighborhood depth when --scope is given — follows both callers and callees |
--enhanced |
off | Enable real-time search + path finder |
--communities |
off | Enable Louvain community detection + colour coding |
--no-browser |
off | Generate without auto-opening the browser |
Scoping large estates
For a big graph (thousands of nodes), rendering the whole thing is rarely
readable — --scope is the way to navigate it. It extracts the N-hop
neighborhood around the matched node(s), following both directions so you
see what a program calls and who calls it:
# PAYROLL, its callers, and its callees (2 hops)
nervapack visualize --scope PAYROLL --hops 2
# Just the immediate neighbors of a copybook
nervapack visualize --scope EMPREC --hops 1
Scoped output defaults to .nervapack/scope_<TARGET>.html so it never clobbers
the full-graph file. Because scoped views are small, physics stays enabled for a
proper interactive layout.
Examples
# Basic visualization
nervapack visualize
# Enhanced — search + path finder
nervapack visualize --enhanced
# Enhanced + community detection (recommended)
nervapack visualize --enhanced --communities
# Custom output path
nervapack visualize --enhanced --output ~/graphs/myproject.html
# Generate without opening browser (server/CI)
nervapack visualize --no-browser
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 · 166 lines · 0 tokens per session scan A 7707b4cb5fdf
visualize 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 1,238 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.