Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/no-fluff/awesome-vibe-coding/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.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 | $0.00746 | $0.00746 |
| Opus 5 | $0.00373 | $0.00373 |
| Sonnet 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 5d 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.
- 5d 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 (58 stars, last pushed 11mo ago), licensed MIT. It adds 746 tokens to every session, about $0.0037 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
claude-code-settings copilot-instructions.md
Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
cherry-studio AGENTS.md
AGENTS.md instructions for CherryHQ/cherry-studio, a project described as: AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs.
tree-sitter-analyzer CLAUDE.md
Claude Code instructions for aimasteracc/tree-sitter-analyzer, covering ruflo — claude code configuration, rules, test quality rules — locked (2026-06-28), t-1: no new test files for existing plugins (blocker) and t-2: no weak assertions — ratchet-enforced (blocker).
ai-agents push-lock.instructions.md
Instructions for rjmurillo/ai-agents, covering one push lock path, must, must not, historical measurements and commit guard.
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.