Borrowing it
Nothing to install: this file belongs to rcarmo/vibes. 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/rcarmo/vibes/main/AGENTS.mdgit clone --depth 1 https://github.com/rcarmo/vibesWrote 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/rcarmo/vibes/agents-md)<a href="https://agentmods.dev/instructions/rcarmo/vibes/agents-md"><img src="https://agentmods.dev/badge/instructions/rcarmo/vibes/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/rcarmo/vibes/agents-md"><img src="https://agentmods.dev/badge/instructions/rcarmo/vibes/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.00617 | $0.00617 |
| Opus 5.5 | $0.00247 | $0.00247 |
| Sonnet 5.5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
vibes 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 21d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibes Python
Cache and scratch paths
The canonical project name is vibes. scripts/project-tmp.sh resolves the
root once before Make exports child temp variables. An absolute
PROJECT_TMP_BASE selects <base>/vibes; the compatible absolute
PROJECT_TMP_ROOT must end in /vibes. If both are supplied they must agree.
Invalid, unsafe or unusable overrides fail without fallback. CI selects usable
${RUNNER_TEMP}/vibes, then the original ${TMPDIR}/vibes, then /tmp/vibes,
even when /workspace/tmp exists. Local runs prefer writable
/workspace/tmp/vibes, then /tmp/vibes. The helper snapshots incoming TMPDIR
as PROJECT_ORIGINAL_TMPDIR and propagates the resolved root to children. The
resolver is vendored; CI needs no /workspace helper. Every selected root uses:
cache/<tool>/for Python bytecode, pytest, pip, uv, Bun, npm and XDG caches.build/for disposable build output.tests/andlogs/for disposable test/log scratch where used.runs/<purpose>/<run-id>/for isolated scratch and test filesystem roots.
The Makefile exports TMPDIR, TMP, TEMP, XDG_CACHE_HOME,
PIP_CACHE_DIR, UV_CACHE_DIR, BUN_INSTALL_CACHE_DIR, npm_config_cache,
PYTHONPYCACHEPREFIX and pytest basetemp/cache options. Set VIBES_RUN_ID
explicitly for reproducible run receipts. Direct commands must use the same
paths. Never use bare /tmp, home caches or ad-hoc top-level temporary paths. Direct
commands can resolve using PROJECT=vibes bash scripts/project-tmp.sh init and
must propagate that root before setting TMPDIR; do not append vibes again to
an already exported run-local TMPDIR.
Retained profiles, logs, receipts and datasets are evidence, not disposable
scratch. Keep publication evidence under docs/evidence/; preserve external
historical evidence until explicitly migrated. Cleanup may remove only confirmed
inactive disposable paths beneath the resolved project root. Never delete another
project's root, retained evidence or files used by active jobs. The existing
clean target removes local Python bytecode/test cache only and does not delete
the project scratch root or evidence.
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.
- 21d ago Changed · -157 lines · -878 tokens per session ced0d20e565f
- 1mo ago First seen · 205 lines · 1,495 tokens per session scan A 5382962a1e65
vibes AGENTS.md is an instructions file published in the GitHub repository rcarmo/vibes (192 stars, last pushed 22d ago), licensed MIT. It adds 617 tokens to every session, about $0.0025 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-09-01.
Other instructions, from other repositories
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).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.