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/statusgit 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/status)<a href="https://agentmods.dev/commands/ramdhavepreetam/nervapack/status"><img src="https://agentmods.dev/badge/commands/ramdhavepreetam/nervapack/status.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.00809 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
status 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nervapack status
Show the health and current state of the local NervaPack graph.
Synopsis
nervapack status [--detailed]
Description
status gives you a quick read on whether your graph is up to date and how healthy it is.
Without --detailed it prints a one-screen summary: node/edge counts, git sync status, and a list of unsynced files. With --detailed it adds a full analytics panel: health score, language distribution, documentation coverage, and the most connected files.
Options
| Option | Description |
|---|---|
--detailed / -d |
Show comprehensive analytics (health score, language breakdown, coverage) |
Examples
# Quick check
nervapack status
# Full analytics panel
nervapack status --detailed
Output — Quick Mode
NervaPack Status:
- Graph loaded: Yes
- Nodes: 1,322
- Edges: 21,833
- Git repo detected: Yes
- Unsynced changes: 2 file(s)
- src/graph/builder.py
- src/graph/retrieval.py
Use --detailed for comprehensive analytics
Output — Detailed Mode
╭────────────── NervaPack Status ──────────────╮
│ Graph Health Score: 85/100 ●●●●●●●●○○ │
│ │
│ 📊 Overview │
│ Nodes: 1,322 │
│ Edges: 21,833 │
│ Files: 78 │
│ Functions: 551 │
│ Classes: 65 │
│ Imports: 628 │
│ │
│ 📚 Language Distribution │
│ Python ████████████████ 100.0% (78) │
│ │
│ 📖 Documentation Coverage │
│ ████████░░░░░░░░ 67.8% (416/616 entities) │
│ │
│ 🔗 Most Connected Files │
│ 1. cli.py (75 edges) │
│ 2. builder.py (48 edges) │
│ 3. retrieval.py (31 edges) │
│ │
│ 🔄 Git Sync Status │
│ ✓ Graph is in sync │
╰────────────────────────────────────────────────╯
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 · 113 lines · 0 tokens per session scan A d99b4b16fc27
status 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 809 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.