vibecoding CLAUDE.md

Project instructions for Claude Code when working on Vibe Coding Digest, a tool that collects technology articles and sends daily email summaries. They describe the project structure, components, and development standards.

In plain words
What is it for?
Use them when developing, testing, or maintaining the Vibe Coding Digest codebase, including its RSS aggregation, OpenAI summarization, SendGrid delivery, and acceptance tests.
Why use it?
They give the coding agent the project context and rules needed to make changes consistently across feeds, summaries, email delivery, AWS search, and tests.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/paulduvall/vibecoding/claude-md
Clone the repo
git clone --depth 1 https://github.com/PaulDuvall/vibecoding
Per session 2,681 This file is loaded in full into every session.
When invoked 2,681 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02681 $0.02681
Opus 5 $0.01340 $0.01340
Sonnet 5 $0.00536 $0.00536
Haiku 4.5 $0.00268 $0.00268

Measured 2d ago against content hash bd6cd79fe5cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vibecoding 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 2d 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.

CLAUDE.md · 288 lines

How it starts

The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Context for Claude Code: CLAUDE.md

This file provides Claude Code with essential project context, rules, and implementation details. This is derived from the Windsurf-specific .windsurfrules.md but adapted for Claude Code workflow.

Project Overview

Vibe Coding Digest is an automated content aggregation and summarization tool that delivers curated, daily email digests of the most relevant developments in AI, developer tools, and emerging technology.

Key Components

  • RSS Feed Aggregation: Multi-source content collection with concurrent processing from 29+ feeds
  • External Configuration: JSON/YAML feed management with categorization and enable/disable controls
  • AI Summarization: OpenAI-powered content summarization with error handling
  • Email Delivery: SendGrid integration for HTML digest delivery
  • AWS Blog Search: Targeted search functionality for AWS-specific content
  • ATDD Test Suite: Comprehensive unit, integration, and acceptance testing with user story traceability

Project Structure

vibecoding/
├── src/                    # Main source package
│   ├── __init__.py        # Package exports and metadata
│   ├── vibe_digest.py     # Main orchestration and entry point
│   ├── models.py          # Data models (DigestItem)
│   ├── feeds.py           # RSS feed management and fetching
│   ├── config_loader.py   # External configuration management
│   ├── summarize.py       # OpenAI summarization logic
│   ├── email_utils.py     # SendGrid email functionality
│   └── aws_blog_search.py # AWS blog search functionality
├── tests/                 # Comprehensive test suite
│   ├── test_vibe_digest.py     # Core functionality tests
│   ├── test_aws_blog_search.py # AWS search tests
│   ├── test_integration.py     # End-to-end pipeline tests
│   ├── test_optimizations.py   # Performance optimization tests
│   └── features/              # ATDD feature specifications
│       ├── digest_workflow.feature      # Main digest scenarios
│       ├── externalized_config.feature  # Configuration scenarios
│       ├── environment.py               # Behave setup
│       └── steps/                       # Step definitions
│           ├── digest_steps.py          # Main workflow steps
│           └── config_steps.py          # Configuration steps
├── docs/                  # Project documentation
│   ├── user_stories.md    # User stories with acceptance criteria
│   ├── traceability_matrix.md # ATDD traceability documentation
│   └── prd.md            # Product Requirements Document
├── .github/
│   └── workflows/
│       └── vibe-coding-digest.yml # CI/CD automation
├── feeds_config.json      # Default external feed configuration
├── .attdrules.md         # ATDD/BDD development guidelines
├── pyproject.toml         # Modern Python package configuration
├── requirements.txt       # Runtime dependencies (includes PyYAML)
└── run.sh                # Development utility script

Read the full file on GitHub · 288 lines

Changes

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.

  1. 2d ago First seen · 288 lines · 2,681 tokens per session scan A bd6cd79fe5cd

Subscribe to this mod's changes

vibecoding CLAUDE.md is an instructions file published in the GitHub repository PaulDuvall/vibecoding (12 stars, last pushed 1y ago), licensed MIT. It adds 2,681 tokens to every session, about $0.0134 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.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens