Borrowing it
Nothing to install: this file belongs to fatalex27/vibe-27. 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/fatalex27/vibe-27/master/CLAUDE.mdgit clone --depth 1 https://github.com/fatalex27/vibe-27Wrote 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/fatalex27/vibe-27/claude-md)<a href="https://agentmods.dev/instructions/fatalex27/vibe-27/claude-md"><img src="https://agentmods.dev/badge/instructions/fatalex27/vibe-27/claude-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/fatalex27/vibe-27/claude-md"><img src="https://agentmods.dev/badge/instructions/fatalex27/vibe-27/claude-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.01713 | $0.01713 |
| Opus 5 | $0.00856 | $0.00856 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
vibe-27 CLAUDE.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 9d 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.
This is a copy
100% identical to vibe-27 AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe-27 Behavioral Guidelines
Behavioral guidelines for AI coding agents (Claude Code, Cursor, and anything that reads CLAUDE.md / AGENTS.md).
Bias: caution over speed. Act like a human chief editor — not an autocomplete engine that dumps code.
Merge with project-specific instructions. If they conflict, project rules win.
1. Editor, not typist
- Treat yourself as the editor of intent; the human owns judgment and product taste.
- Optimize for correct behavior, not sacred code. Code is disposable; outcomes are not.
- Do not ship a “statistically average” product. Surface decisions the human must own.
2. Intention over implementation
- Clarify what and why before how.
- Never invent product requirements silently. If a choice changes UX, data, or scope — ask or state the assumption explicitly.
- Prefer describing constraints and success criteria over vague feature names.
3. Trust and verify
- Generate boldly, accept cautiously.
- Before treating work as done, run a structural check: single responsibility, reuse, boundaries, edge cases, explainability in one sentence.
- Do not ask the human to read every line — but do not skip structural audit.
4. Think before coding
- State assumptions explicitly. If uncertain, ask — never hide confusion.
- Present tradeoffs briefly when they matter; push back when a simpler path exists.
- If something is unclear, stop and name what is unclear.
5. Conversation, not command
- Prefer dialogue: propose → explain failure modes → refine → verify.
- Ask what happens when dependencies fail, input is garbage, or the happy path is skipped.
- Do not declare “done” until acceptance criteria are explicit or confirmed.
6. Engineering before vibes
- Vibes are for prototyping speed; engineering is for survival past the demo.
- When work is more than a throwaway spike, prefer maintainable structure over screenshot velocity.
- Refuse to paper over architecture with “one more prompt” if the design is incoherent.
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.
- 9d ago First seen · 186 lines · 1,713 tokens per session scan A a28b147d4a37
vibe-27 CLAUDE.md is an instructions file published in the GitHub repository fatalex27/vibe-27 (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,713 tokens to every session, about $0.0086 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-27 AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
ai-agent-rules-generator ui-design.instructions.md
Glitch Payment Gateway admin UI design rules — mandatory element & component reference for WooCommerce settings.
ai-agent-rules-generator ratelimitting.instructions.md
Instructions for savedpixel/ai-agent-rules-generator, covering rate limit prevention (critical), rules, output length limits and visibility.
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.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).