audit

A command that performs a full audit of a software repository, including its source, checks, evidence, and reported findings.

In plain words
What is it for?
Use it to inspect a repository, branch, pull request, or workspace, run selected checks, produce reports, and fail CI when configured thresholds are missed.
Why use it?
It brings repository review into one repeatable command and can apply quality limits or CI, the automated checks run for code changes.

Command

Install

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.

agentmods
npx agentmods add commands/nordbyte/repovista/audit
Clone the repo
git clone --depth 1 https://github.com/nordbyte/RepoVista
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00518
Opus 5 $0.00000 $0.00259
Sonnet 5 $0.00000 $0.00104
Haiku 4.5 $0.00000 $0.00052

Measured 2d ago against content hash 759a1ef88cdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

audit 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.

docs/commands/audit.md · 43 lines

What it actually says

audit

Run a full repository audit. repovista with no command is an alias for repovista audit.

Usage

repovista [options]
repovista audit [options]

Common options

  • Source and scope: --github-repo, --github-ref, --since, --pr, --base, --workspace, --all-workspaces, --workspace-matrix
  • Provider: --provider, --model, --profile, --reasoning, --fast, --sandbox
  • Mode: --audit-profile, --review-mode, --bug-findings
  • Quality: --run-checks, --check, --strict-reports, --repair-reports, --repair-attempts, --deep-review
  • Output: --out, --resume, --export, --json, --keep-logs
  • CI gates: --ci, --fail-on-critical, --fail-on-drift, --fail-on-weak-evidence, --min-quality-score, --max-critical, --max-high, --max-medium

See CLI options for every flag and accepted value.

Examples

repovista audit
repovista audit --model gpt-5.5
repovista audit --provider claude --model sonnet --reasoning high
repovista audit --github-repo nordbyte/RepoVista
repovista audit --github-repo https://github.com/nordbyte/RepoVista --github-ref v0.4.0
repovista audit --bug-findings
repovista audit --github-repo nordbyte/RepoVista --bug-findings
repovista audit --since origin/main
repovista audit --ci --json --fail-on-critical
repovista audit --phase risk-and-bug --phase summary

Output

The default output root is .repovista. Each run gets a timestamped directory with index.md, phase reports, JSON summaries, exports, findings, and metadata.

With --bug-findings, RepoVista writes the Risk/Bug report and the supporting JSON/state/export artifacts needed to inspect findings and publish selected ones as GitHub issues or PRs. It does not generate architecture, code-quality, roadmap, summary, or deep-review reports for that run.

Changes

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.

  1. 2d ago First seen · 43 lines · 0 tokens per session scan A 759a1ef88cdb

Subscribe to this mod's changes

audit 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 518 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.