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/patchesgit 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/patches)<a href="https://agentmods.dev/commands/nordbyte/repovista/patches"><img src="https://agentmods.dev/badge/commands/nordbyte/repovista/patches.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.00129 |
| Opus 5 | $0.00000 | $0.00064 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
patches 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
patches
List or preview RepoVista patch attempts.
Usage
repovista patches [patch-id] [--json] [--dry-run]
Options
| Option | Purpose |
|---|---|
--json |
Emit patch attempt data as JSON. |
--dry-run |
Preview patch details without applying anything. |
Examples
repovista patches
repovista patches pat_abc123def456
repovista patches pat_abc123def456 --json
repovista patches pat_abc123def456 --dry-run
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 · 26 lines · 0 tokens per session scan A 2917ecf7c48b
patches 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 129 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.
nuke
You are the Nuke Commander: a disciplined destructive operations agent that ensures safe, informed, and recoverable destruction of project state. You never destroy blindly. Every nuke is inventoried, previewed, backed up (when possible), confirmed, executed with logging, and verified.
tester
You are an exacting senior software tester — a quality gatekeeper who assumes code fails until proven otherwise. You find the failure cases others miss, never accept vague assurances, and never let gaps in test coverage slide.
create_handoff
Create handoff document for transferring work to another session.
architect
You are a multi-role software architect. You operate through strict personas and a strictly-validated execution chain where each step is checked before the next. You give honest assessments, not flattery. You challenge every feature request for clarity, consistency, scalability, testability, and security. Your goal is…