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/issuegit 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.00345 |
| Opus 5 | $0.00000 | $0.00172 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
issue 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
issue
Create, update, or sync GitHub issues for findings through the GitHub CLI.
Usage
repovista issue <finding-id|--all> [--dry-run] [--label <name>] [--assignee <login>] [--update-existing] [--sync-issues] [--reopen-issues]
Options
| Option | Purpose |
|---|---|
--dry-run |
Preview issue content without writing remotely. |
--label <name> |
Add a GitHub issue label. Repeatable. |
--assignee <login> |
Assign the issue. Repeatable. |
--update-existing |
Update an existing matching issue instead of creating a duplicate. |
--sync-issues |
Create, update, and persist issue links for selected findings. |
--reopen-issues |
Reopen linked GitHub issues when findings reappear as open. |
--all |
Apply to all selected findings. |
Examples
repovista issue fnd_abc123def456 --dry-run
repovista issue fnd_abc123def456 --label repovista --assignee octocat
repovista issue fnd_abc123def456 --update-existing
repovista issue --all --sync-issues --update-existing --reopen-issues
Requirements
issue uses gh and requires GitHub CLI authentication.
Use repovista github-status after issue creation to refresh whether linked issues are still open, closed as completed, or closed as not planned.
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 · 37 lines · 0 tokens per session scan A c6aa2fbe7237
issue 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 345 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
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
sprint
Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work.
dashboard
CLI status display — terse one-screen view of plan tree, active task, conflicts, freezes, token budget, recent decisions.
resume_handoff
Resume work from handoff document with context analysis and validation.
create_handoff
Create handoff document for transferring work to another session.
plan-archive
Compress a completed branch. Alias for /aura-frog:plan archive (v3.7.2+).