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/majiayu000/vibeguard/checkgit 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/check)<a href="https://agentmods.dev/commands/majiayu000/vibeguard/check"><img src="https://agentmods.dev/badge/commands/majiayu000/vibeguard/check.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.00018 | $0.01351 |
| Opus 5 | $0.00009 | $0.00675 |
| Sonnet 5 | $0.00004 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
VibeGuard: Check 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Concept
- Quickly and non-invasively check the code health of your current project
- Automatically detect the project language and run the corresponding guard script
- Output structured reports, sorted by severity
- Can be run at any time during the coding process to verify that modifications do not introduce new problems
Guardrails
- Read-only operation, no modification of any files
- No automatic fixes — just report the problem and fix it at the user's discretion
- If the user provides a preflight constraint set baseline, report changes compared to the baseline
Steps
-
Determine project path and language
- Project path: User parameters > Current working directory
- Language detection:
Cargo.toml→ Rustpackage.json→ TypeScript/JavaScriptpyproject.toml/setup.py/requirements.txt→ Pythongo.mod→ Go
- Locate the vibeguard installation path (
~/Desktop/code/AI/tools/vibeguard/or via theVIBEGUARD_DIRenvironment variable)
-
Run universal guards and the guard script corresponding to the language
Universal Project Checks:
bash ${VIBEGUARD_DIR}/guards/universal/check_doc_overload.sh <project_dir>Rust Project:
bash ${VIBEGUARD_DIR}/guards/rust/check_unwrap_in_prod.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/rust/check_duplicate_types.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/rust/check_nested_locks.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/rust/check_workspace_consistency.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/rust/check_single_source_of_truth.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/rust/check_semantic_effect.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/rust/check_taste_invariants.sh <project_dir>TypeScript/JavaScript Project:
# eslint_guards: Automatically run npx eslint --max-warnings=0 when the project has eslint configuration. bash ${VIBEGUARD_DIR}/guards/typescript/check_any_abuse.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/typescript/check_console_residual.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/typescript/check_component_duplication.sh <project_dir>Python Project:
python3 ${VIBEGUARD_DIR}/guards/python/check_duplicates.py <project_dir> python3 ${VIBEGUARD_DIR}/guards/python/check_naming_convention.py <project_dir> python3 ${VIBEGUARD_DIR}/guards/python/test_code_quality_guards.pyGo Project:
go vet ./... # vet(MCP go.vet) bash ${VIBEGUARD_DIR}/guards/go/check_error_handling.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/go/check_goroutine_leak.sh <project_dir> bash ${VIBEGUARD_DIR}/guards/go/check_defer_in_loop.sh <project_dir>Each guard operates independently, and the failure of one does not affect other guards.
-
Run Compliance Check
bash ${VIBEGUARD_DIR}/scripts/verify/compliance_check.sh <project_dir> -
Summary Report
Output format:
══════════════════════════════════ VibeGuard Health Report Project: <project_name> Date: <date> ══════════════════════════════════ ┌─ RS-03 unwrap/expect ─────────┐ │ Found: 50 │ │ Severity: Moderate │ └────────────────────────────────┘ ┌─ RS-05 Repeat Type ──────────────┐ │ Found: 2 places │ │ Severity: Moderate │ │ - SearchQuery (server, core) │ │ - AppState (desktop, server) │ └────────────────────────────────┘ ┌─ RS-01 Nested Lock ─────────────────┐ │ Found: 0 places │ │ Severity: ✓ Pass │ └────────────────────────────────┘ ┌─ RS-06 cross-entry consistency ──────────┐ │ Found: 2 places │ │ Severity: Moderate │ └────────────────────────────────┘ ┌─ Compliance Inspection ─────────────────────┐ │ PASS: 3 WARN: 3 FAIL: 2 │ └────────────────────────────────┘ Overall rating: 6.5/10
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 · 137 lines · 18 tokens per session scan A 45b473614562
VibeGuard: Check is a command published in the GitHub repository majiayu000/vibeguard (41 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,351 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
lint-status
Show AgentLint status — active rules, violations this session.
investigate
Systematic root-cause debugging — find the cause before writing any fix.
ops
You are the Ops Tooling Generator, an operational tooling specialist. You generate production-ready admin panels, debug overlays, and feedback systems for completed projects.
hotfix
Emergency fix mode. Bypasses full pipeline. Smoke test only. Creates mandatory follow-up story.
preflight
You are the Codebase Comprehension Pre-Flight. You give agents a structural model of existing code BEFORE they write, attacking the framework's #1 failure class — the Frontend-Backend Contract Mismatch. You are backed by the sfcodemap MCP tool (engine: mcp-server/src/agents/codemap/). You are a sibling to the…
patterns
List makoto's integrity pattern catalog (read-only).