newsletter: Instructions file for Claude Code

CLAUDE.md

newsletter CLAUDE.md is an instructions file for Claude Code from andreapollastri/newsletter. It costs 3,401 tokens per session, scanned A, original, MIT.

Development instructions for a Laravel newsletter application, including its PHP and Laravel-related tools and versions.

In plain words
What is it for?
They guide work on the newsletter app and activate Laravel-specific practices for PHP code such as controllers, models, migrations, policies, jobs, and scheduled tasks.
Why use it?
They give coding agents the project context and require relevant Laravel guidance when changing application code.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is andreapollastri/newsletter's own configuration. It tells Claude Code how to work on newsletter itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything newsletter configures →

Reuse

Borrowing it

Nothing to install: this file belongs to andreapollastri/newsletter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/andreapollastri/newsletter/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/andreapollastri/newsletter

Made for: Claude Code.

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

agentmods badge for newsletter CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/andreapollastri/newsletter/claude-md/github.svg)](https://agentmods.dev/instructions/andreapollastri/newsletter/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/andreapollastri/newsletter/claude-md"><img src="https://agentmods.dev/badge/instructions/andreapollastri/newsletter/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.

agentmods 80×15 button for newsletter CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/andreapollastri/newsletter/claude-md"><img src="https://agentmods.dev/badge/instructions/andreapollastri/newsletter/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,401 This file is loaded in full into every session.
When invoked 3,401 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.03401 $0.03401
Opus 5 $0.01700 $0.01700
Sonnet 5 $0.00680 $0.00680
Haiku 4.5 $0.00340 $0.00340

Measured 9d ago against content hash 90eea797f029, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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

CLAUDE.md · 324 lines

How it starts

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

Laravel Boost Guidelines

The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to ensure the best experience when building Laravel applications.

Foundational Context

This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions.

  • php - 8.5
  • filament/filament (FILAMENT) - v5
  • laravel/framework (LARAVEL) - v13
  • laravel/prompts (PROMPTS) - v0
  • livewire/livewire (LIVEWIRE) - v4
  • laravel/boost (BOOST) - v2
  • laravel/mcp (MCP) - v0
  • laravel/pail (PAIL) - v1
  • laravel/pint (PINT) - v1
  • laravel/sail (SAIL) - v1
  • phpunit/phpunit (PHPUNIT) - v12

Skills Activation

This project has domain-specific skills available. You MUST activate the relevant skill whenever you work in that domain—don't wait until you're stuck.

  • laravel-best-practices — Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

Conventions

  • You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, and naming.
  • Use descriptive names for variables and methods. For example, isRegisteredForDiscounts, not discount().
  • Check for existing components to reuse before writing a new one.

Read the full file on GitHub · 324 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. 9d ago First seen · 324 lines · 3,401 tokens per session scan A 90eea797f029

Subscribe to this mod's changes

newsletter CLAUDE.md is an instructions file published in the GitHub repository andreapollastri/newsletter (11 stars, last pushed 3d ago), licensed MIT. It adds 3,401 tokens to every session, about $0.0170 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-31.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 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,153 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

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

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,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens