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/cleangit 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/clean)<a href="https://agentmods.dev/commands/ramdhavepreetam/nervapack/clean"><img src="https://agentmods.dev/badge/commands/ramdhavepreetam/nervapack/clean.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.00827 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
clean 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nervapack clean
Remove ingested graph data and start fresh.
Synopsis
nervapack clean [OPTIONS]
Description
clean deletes the files NervaPack writes into .nervapack/ so you can re-ingest from scratch. Use it when:
- You ran
nervapack ingest .multiple times and have duplicate embeddings in ChromaDB - You ingested the wrong directory and want to start over
- The graph or vector store is corrupt or stale
- You want to reduce disk space used by
.nervapack/
clean never touches memory.db (your agent memory store) — decisions, facts, and sessions are always preserved.
Options
| Option | Description |
|---|---|
--vectors |
Wipe the ChromaDB vector store only (chroma_db/) |
--graph |
Delete graph.graphml only |
--history |
Clear query_history.jsonl and graph_history.jsonl |
--all |
Everything above — full wipe, keeps memory.db |
--yes / -y |
Skip the confirmation prompt (useful in scripts/CI) |
--path PATH |
Project root where .nervapack/ lives (default: .) |
Examples
Fix duplicate embeddings after multiple ingests
nervapack clean --vectors
nervapack ingest .
Delete everything and re-ingest from scratch
nervapack clean --all
nervapack ingest .
Non-interactive full wipe (CI / scripting)
nervapack clean --all --yes
nervapack ingest .
Clean a different project's graph
nervapack clean --all --path /path/to/project
What gets deleted
| Flag | Files removed |
|---|---|
--vectors |
.nervapack/chroma_db/ (the entire ChromaDB directory) |
--graph |
.nervapack/graph.graphml |
--history |
.nervapack/query_history.jsonl, .nervapack/graph_history.jsonl |
--all |
All of the above |
Never deleted: .nervapack/memory.db (agent memory — bi-temporal SQLite store).
Output
The following will be permanently deleted:
What Path Size
──────────────────────────────────────────────────────────
ChromaDB vector store ./.nervapack/chroma_db 38.1 MB
Graph (graph.graphml) ./.nervapack/graph.graphml 1.4 MB
Note: memory.db (agent memory) is never touched by clean.
Proceed? [y/n]: y
✓ Deleted: ChromaDB vector store
✓ Deleted: Graph (graph.graphml)
Clean complete. Run nervapack ingest . to rebuild.
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 · 130 lines · 0 tokens per session scan A 7d91e7803a46
clean is a command published in the GitHub repository ramdhavepreetam/NervaPack (1 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 827 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.