Borrowing it
Nothing to install: this file belongs to PIsberg/vibetags. 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/PIsberg/vibetags/main/AGENTS.mdgit clone --depth 1 https://github.com/PIsberg/vibetagsWrote 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/pisberg/vibetags/agents-md)<a href="https://agentmods.dev/instructions/pisberg/vibetags/agents-md"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/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/pisberg/vibetags/agents-md"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/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.03854 | $0.03854 |
| Opus 5.5 | $0.01542 | $0.01542 |
| Sonnet 5.5 | $0.00771 | $0.00771 |
| Haiku 4.5 | $0.00385 | $0.00385 |
Grade A, and why
vibetags 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 14d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeTags — Agent Instructions
Start with llms.txt for a map of this repo's docs and layout.
The primary agent briefing is CLAUDE.md — build commands, build
order, architecture invariants, and the <project_guardrails> block (locked
files, contract-frozen signatures, hot-path constraints). It is tool-neutral
despite the name: read and follow it whichever agent you are.
Ground rules for any agent working here:
- Respect the guardrails in CLAUDE.md: never edit files/elements listed as locked, never change contract-frozen signatures.
- Never hand-edit content between
VIBETAGS-START/VIBETAGS-ENDmarkers in any file — it is generated by this project's own annotation processor. - Build order matters:
vibetags-annotations→vibetags→vibetags-bom→example. Always build from the subproject's own directory. - Reference docs load on demand:
docs/ANNOTATIONS.md(annotation reference),docs/PLATFORMS.md(output-file table),docs/TESTS.md(test coverage map),docs/ARCHITECTURE.md(deep dive),docs/DEPENDENCIES.md(third-party artifacts).
Note: this file is intentionally not VibeTags-managed — other AI config files exist at the root, so the processor's AGENTS.md sole-file fallback leaves it untouched.
AUTO-GENERATED AI RULES
Generated by VibeTags | https://github.com/PIsberg/vibetags
Do not edit manually.
LOCKED FILES (DO NOT EDIT)
- se.deversity.vibetags.processor.AIGuardrailProcessor.generateFiles(): Step order is load-bearing: fingerprint check → sidecar write → sidecar read → merge → file write → cache flush; reordering steps silently skips regeneration or corrupts multi-module output
- se.deversity.vibetags.processor.internal.TransitiveManifest.RESOURCE_PACKAGE: Must stay a valid Java package name. javac's CLASS_PATH location skips archive directories that are not package identifiers, so moving these manifests under META-INF/ leaves Filer.getResource listing zero entries and transitive discovery fails silently while the conventional location looks correct. TransitiveManifestPathTest pins the working path.
- se.deversity.vibetags.processor.model.GuardrailAnnotations.ALL: Append only. This order fixes the insertion order of every LinkedHashSet downstream, so reordering or removing an entry rewrites generated files in every consuming build, with nothing failing to name the cause. BuildFingerprint hashes in its own separately pinned order; the two are not the same list and must not be aligned.
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.
- 14d ago Changed · +1 lines · +93 tokens per session b62be2173403
- 15d ago Changed · +34 tokens per session 518a071555de
- 16d ago Changed · +3 lines · +270 tokens per session 8eca1ce5f74d
- 25d ago Changed · +1 lines · +67 tokens per session dd36c6257cb2
- 26d ago Changed · -11 lines · -49 tokens per session e617de1c300b
- 1mo ago Changed · -29 lines · -413 tokens per session c63e0929a9a4
- 1mo ago Changed · +44 lines · +612 tokens per session bc4cfb37266d
- 1mo ago Changed · +6 tokens per session 3c233bb21e24
- 1mo ago Changed · +2 lines · +232 tokens per session f95c601eb9f2
- 1mo ago First seen · 104 lines · 3,002 tokens per session scan A 72011c44646a
vibetags AGENTS.md is an instructions file published in the GitHub repository PIsberg/vibetags (25 stars, last pushed today), licensed MIT. It adds 3,854 tokens to every session, about $0.0154 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
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.