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/live-truth.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/live-truth)<a href="https://agentmods.dev/commands/majiayu000/vibeguard/live-truth"><img src="https://agentmods.dev/badge/commands/majiayu000/vibeguard/live-truth/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/majiayu000/vibeguard/live-truth"><img src="https://agentmods.dev/badge/commands/majiayu000/vibeguard/live-truth.svg" alt="Reviewed on agentmods" width="80" 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.00553 |
| Opus 5 | $0.00010 | $0.00277 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
VibeGuard: Live Truth 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 9d 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 Concept
- Turn stateful claims like "latest", "ready to merge", "merged", "running", "deployed", or "published" into fresh evidence.
- Separate observed facts from inferences and unresolved gaps.
- Produce a compact artifact that can be pasted into a final answer or PR comment.
Steps
-
Pick the claim type from the user request:
latest: current git branch freshness against a fetched remote refpr-ready: PR state, draft state, mergeability, CI checks, and review evidencemerged: remote PR state plus optional local target branch containmentrunning: OS process identity plus optional health endpointdeployed: live URL/health endpoint plus optional version/ref textpublished: registry/package metadata plus tag, commit, or artifact checksum parity
-
Run the reusable verifier:
python3 ~/vibeguard/scripts/live_truth.py checklist python3 ~/vibeguard/scripts/live_truth.py latest --repo <repo_dir> --remote origin --branch main python3 ~/vibeguard/scripts/live_truth.py pr-ready --repo <owner/name> --pr <number> python3 ~/vibeguard/scripts/live_truth.py merged --repo <owner/name> --pr <number> --repo-path <repo_dir> --remote origin --branch main python3 ~/vibeguard/scripts/live_truth.py running --pid <pid> --health-url <url> python3 ~/vibeguard/scripts/live_truth.py deployed --url <url> --expect-text <version-or-ref> python3 ~/vibeguard/scripts/live_truth.py published --fixture <metadata.json> -
Report the verifier output without upgrading gaps into facts:
LIVE-TRUTH <claim> verdict: pass | fail | gap facts: - ... inferences: - ... unresolved_gaps: - ...
Rules
- Fresh evidence is required for mutable claims; memory alone is not proof.
- A
gapverdict must be stated as unresolved, not treated as success. - A
failverdict blocks claims that the state is ready, merged, live, current, or published.
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.
- 9d ago First seen · 51 lines · 20 tokens per session scan A fd8a4bbc60b2
VibeGuard: Live Truth 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 553 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.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
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.