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/reviewgit clone --depth 1 https://github.com/nordbyte/RepoVistaWrote 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/nordbyte/repovista/review)<a href="https://agentmods.dev/commands/nordbyte/repovista/review"><img src="https://agentmods.dev/badge/commands/nordbyte/repovista/review.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.00150 |
| Opus 5 | $0.00000 | $0.00075 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
review 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.
What it actually says
review
Review one RepoVista run for report quality, evidence, and stale state risks.
Usage
repovista review <run-dir> [--json]
Options
--jsonemits machine-readable review output.
Examples
repovista review .repovista/2026-05-21T10-00-00-000Z
repovista review .repovista/2026-05-21T10-00-00-000Z --json
When to use it
Use review after a run has been created when you want to evaluate evidence quality, stale checkout signals, report completeness, and machine-readable artifact health.
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 · 25 lines · 0 tokens per session scan A e31fbfe53faa
review 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 150 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.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
create_handoff
Create handoff document for transferring work to another session.
lrn
Execute the /vibeguard:learn command. $ARGUMENTS.
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".