Borrowing it
Nothing to install: this file belongs to no-fluff/awesome-vibe-coding. 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/no-fluff/awesome-vibe-coding/main/CLAUDE.mdgit clone --depth 1 https://github.com/no-fluff/awesome-vibe-codingWrote 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/no-fluff/awesome-vibe-coding/claude-md)<a href="https://agentmods.dev/instructions/no-fluff/awesome-vibe-coding/claude-md"><img src="https://agentmods.dev/badge/instructions/no-fluff/awesome-vibe-coding/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/no-fluff/awesome-vibe-coding/claude-md"><img src="https://agentmods.dev/badge/instructions/no-fluff/awesome-vibe-coding/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.00746 | $0.00746 |
| Opus 5.5 | $0.00298 | $0.00298 |
| Sonnet 5.5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
awesome-vibe-coding 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 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
awesome-vibe-coding TOML Data Format
This repository uses a data-driven approach where all entries are stored in data.toml and the README.md is automatically generated from this structured data.
TOML Structure
The data.toml file contains five main sections corresponding to the categories in the README:
Section Mappings
- Agents →
[[agents]] - Vibe-coding apps →
[[apps]] - Agent interfaces →
[[interfaces]] - Tools and MCP servers →
[[tools]] - Vibe-coding workflows →
[[workflows]]
Entry Format
Each entry follows this TOML structure:
[[section_name]]
name = "Project Name"
website = "https://example.com/"
repo = "https://github.com/user/repo"
open_source = true
summary = "Headline up to 20 words."
detail = "One concise paragraph expanding on capabilities and use-cases."
category = "Relevant Category"
Required Fields
name: Project name (≥ 2 characters)summary: Headline description (≤ 20 words)detail: Detailed description (1-3 sentences)open_source: Boolean indicating if the project is open sourcecategory: Category classification
Optional Fields
website: Project website URLrepo: GitHub repository URLhot: Boolean flag for exceptional/trending resources (maintainer-only)
Note: Either website or repo must be provided.
Category Classifications
Agents
Core coding agents that use LLMs to write/modify code. Typically CLI/daemon/desktop/server applications that expose tools for code editing, running, testing, and repository operations.
Vibe-coding Apps
Applications that build significant product features on top of agents, such as project management, planning, product roadmapping, collaboration, and dashboards.
Agent Interfaces
Primarily GUI/UX wrappers around existing agents that add convenience rather than core capabilities. Keywords include "GUI", "Electron app", "web UI for...".
Tools and MCP Servers
Plugins, subagents, slash commands, MCP servers, and IDE extensions that extend agents but are not standalone coding agents.
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 First seen · 92 lines · 746 tokens per session scan A 696eb5470d32
awesome-vibe-coding CLAUDE.md is an instructions file published in the GitHub repository no-fluff/awesome-vibe-coding (59 stars, last pushed 1y ago), licensed MIT. It adds 746 tokens to every session, about $0.0030 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
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
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).