Borrowing it
Nothing to install: this file belongs to majiayu000/vibeguard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/majiayu000/vibeguard/main/.claude/commands/vibeguard/stats.mdgit clone --depth 1 https://github.com/majiayu000/vibeguardWrote 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/majiayu000/vibeguard/stats)<a href="https://agentmods.dev/commands/majiayu000/vibeguard/stats"><img src="https://agentmods.dev/badge/commands/majiayu000/vibeguard/stats.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.1 | $0.00020 | $0.00372 |
| Opus 5 | $0.00010 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
VibeGuard: Stats 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 6d 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
Core Features
- Analyze hook trigger logs in
~/.vibeguard/events.jsonl - Output interception/warning/release statistics, distribution by hook, top 5 reasons, and daily trigger volume
- Supports
healthsnapshot mode: risk rate, Top risk hook, Top 10 recent risk events - Help users understand whether VibeGuard is working and what is blocked
Steps
-
Run the corresponding script according to the parameters:
if [[ "${ARGUMENTS:-}" == health* ]]; then health_arg="${ARGUMENTS#health}" health_arg="${health_arg#"${health_arg%%[![:space:]]*}"}" bash ~/Desktop/code/AI/tools/vibeguard/scripts/hook-health.sh "${health_arg:-24}" else bash ~/Desktop/code/AI/tools/vibeguard/scripts/stats.sh $ARGUMENTS fiParameter description:
- No parameters: Last 7 days
- Number (e.g. 30): Last N days
all: all historyhealth: health snapshot of the last 24 hourshealth 72: Health snapshot of the last 72 hours
-
Display the statistical results to the user. If there is an exception (such as interception is 0 but has been used for a period of time), you will be reminded to check whether the hooks configuration is correct.
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.
- 6d ago First seen · 35 lines · 20 tokens per session scan A 9c026752b80a
VibeGuard: Stats is a command published in the GitHub repository majiayu000/vibeguard (41 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 372 once invoked, about $0.0001 per session on Opus 5. 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-30.
Other commands, from other repositories
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.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
init
Install the formatters this repository needs, with every command visible before it runs.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.