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/nordbyte/repovista/settingsgit clone --depth 1 https://github.com/nordbyte/RepoVistaWhat 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.00199 |
| Opus 5 | $0.00000 | $0.00100 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
settings 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.
What it actually says
settings
Edit, read, set, or reset persisted default settings.
Usage
repovista settings
repovista settings get [key]
repovista settings set <key> <value>
repovista settings reset [key]
Examples
repovista settings
repovista settings get
repovista settings get model
repovista settings set model gpt-5.5
repovista settings set reasoning xhigh
repovista settings set fastMode on
repovista settings set bugFindingsOnly on
repovista settings set exportFormats sarif,html
repovista settings reset reasoning
repovista settings reset
Storage
Settings are stored in ~/.config/repovista/settings.json unless REPOVISTA_CONFIG points to another file.
Reference
See Settings keys for every key and accepted type.
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 · 36 lines · 0 tokens per session scan A 2c7176d0adc8
settings is a command published in the GitHub repository nordbyte/RepoVista (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 199 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
brooks-audit
Run a Brooks-Lint architecture audit.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
create_handoff
Create handoff document for transferring work to another session.