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.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.01335 | $0.01335 |
| Opus 5 | $0.00668 | $0.00668 |
| Sonnet 5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
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 7d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Scope
This file applies to the whole repository unless a nested AGENTS.md overrides it.
VibeGuard is an anti-hallucination rules, hooks, runtime, installer, and workflow repository. There is no ORM, front-end framework, or microservices layer in this project.
Start Here
- Check
git status --short --branchand preserve unrelated work. - Search before adding files, functions, rules, hooks, workflows, or tests.
- Read
docs/directory-map.mdbefore moving files or changing public paths. - Read
docs/specs/README.mdandplan/README.mdbefore treating documents as pending work. - For runtime, hook, setup, or workflow changes, read the closest scoped
CLAUDE.md. - For GitHub work, verify live remote state and use an isolated worktree based on the current remote base.
Core Rules
- Keep names
snake_caseunless an external API boundary requirescamelCase. - Do not swallow errors silently. User-visible missing data or wrong output must fail loudly.
- Do only the requested scope; avoid opportunistic refactors.
- Preserve VibeGuard's core enforcement model: rules, hooks, setup scripts, and
vibeguard-runtime/are the source implementation. - Treat plugin, pack, docs, and workflow changes as distribution layers unless a current design explicitly changes runtime behavior.
- High-context files such as
AGENTS.md,CLAUDE.md,.claude/settings*.json, setup scripts, hooks, and workflow contracts require explicit intent. - Never add AI-generated markers or hidden attribution text to commits, docs, or generated artifacts.
Delivery Policy
- Implement clear, bounded tasks directly. Do not require a spec, routing packet, schema, receipt, runtime snapshot, or multi-agent handoff for ordinary work.
- Clarify only when a missing choice would materially change the result or make execution unsafe.
- Write a plan for major architecture, migration, cross-system policy work, or when the user explicitly requests one.
- A normal spec is at most two files and about 300 lines total. Docs-only changes, small bugs, and explicit mechanical edits are spec-exempt.
- Do not create validators for spec validators or add process artifacts merely to satisfy another process artifact.
- Use focused tests while iterating. Run the broader relevant suite before submission; leave exhaustive platform coverage to CI.
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.
- 7d 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 (41 stars, last pushed today), licensed MIT. It adds 1,335 tokens to every session, about $0.0067 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 instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.