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/github-statusgit 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.00417 |
| Opus 5 | $0.00000 | $0.00209 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
github-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 yesterday.
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
github-status
Refresh linked GitHub issue and pull request status for RepoVista findings.
Usage
repovista github-status [finding-id|--all] [--run <run-id|dir>] [--json]
Without a finding id or --all, RepoVista refreshes findings that already have a linked GitHub issue or pull request.
Options
| Option | Purpose |
|---|---|
<finding-id> |
Refresh one finding. Comma-separated ids are accepted. |
--all |
Refresh all findings, including linked and unlinked findings. |
| `--run <run-id | dir>` |
--json |
Emit the sync result and refreshed findings as JSON. |
Status mapping
Issue state is stored as open, closed, or unknown. Closed issues also keep GitHub's reason when available, such as completed or not-planned.
Pull request state is stored as open, closed, merged, or unknown. Draft PRs render as PR draft in the TUI.
Remote GitHub status does not overwrite the RepoVista finding lifecycle status. A merged PR is a signal for triage, but the finding remains open, fixed, false-positive, wont-fix, or uncertain until you update it.
Examples
repovista github-status fnd_abc123def456
repovista github-status fnd_abc123def456 --run 2026-05-21T10-00-00-000Z
repovista github-status --all --run 2026-05-21T10-00-00-000Z --json
The repovista reports and repovista findings-ui TUIs expose the same refresh path with g for the selected finding and G for all visible findings.
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.
- yesterday First seen · 39 lines · 0 tokens per session scan A 90205b4b1113
github-status 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 417 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.