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/AGENTS.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/instructions/majiayu000/vibeguard/agents-md)<a href="https://agentmods.dev/instructions/majiayu000/vibeguard/agents-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/vibeguard/agents-md/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/instructions/majiayu000/vibeguard/agents-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/vibeguard/agents-md.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.00521 | $0.00521 |
| Opus 5.5 | $0.00208 | $0.00208 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
vibeguard AGENTS.md 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 1mo 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
VibeGuard v2 is a Rust CLI with a curated rule library and native integrations. This file applies to the repository.
- Check
git status --short --branchand preserve unrelated work. Search before adding code or files. - Read the directory map before moving public paths and the runtime contract before changing hooks or installation.
- Keep the runtime in Rust. The optional plugin is a help entry point, not another runtime.
- Keep one writable session per worktree. Use read-only helpers for independent tasks when delegation is authorized.
- Follow the user's scope and existing authorization. Inspection alone does not authorize mutation.
- No compatibility shims, old ID aliases, workflow engines, or semantic regex scanners without an explicit new requirement.
- Keep errors visible; unavailable evidence is not success. Preserve valid tests and user-managed instructions/settings.
- Changes to installation, instructions, permissions, and release behavior require explicit task intent.
- Use snake_case internally; native protocol fields retain host spelling.
- Use host-native execution and permissions. Do not add an agent-loop proxy.
- Do not install globally, publish, push, merge, or send messages without authorization.
- Major architecture needs a concise plan, at most two files and about 300 lines. Ordinary work needs no process packet.
- Review at most twice. Stop after relevant checks pass and no findings remain.
Validation
From the repository root:
| Change | Focused verification |
|---|---|
| Rust | cargo check --locked --manifest-path vibeguard-runtime/Cargo.toml and cargo test --locked --manifest-path vibeguard-runtime/Cargo.toml |
| Rules | python3 scripts/generate_rule_docs.py then bash scripts/ci/validate-rules.sh |
| Docs | bash scripts/ci/validate-doc-paths.sh and bash scripts/ci/validate-doc-command-paths.sh |
| Python tooling | python3 -m unittest discover -s tests -p 'test_*.py' |
| Multiple surfaces / submission | bash scripts/local-contract-check.sh |
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.
- 1mo ago Changed · -57 lines · -814 tokens per session 69d98f6d49bc
- 1mo ago First seen · 91 lines · 1,335 tokens per session scan A 633d8ba622f9
vibeguard AGENTS.md is an instructions file published in the GitHub repository majiayu000/vibeguard (44 stars, last pushed 7d ago), licensed MIT. It adds 521 tokens to every session, about $0.0021 per session on Opus 5.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 instructions, from other repositories
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).