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/spatie/freek.dev/claude-mdgit clone --depth 1 https://github.com/spatie/freek.devWrote 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/spatie/freek.dev/claude-md)<a href="https://agentmods.dev/instructions/spatie/freek.dev/claude-md"><img src="https://agentmods.dev/badge/instructions/spatie/freek.dev/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.03946 | $0.03946 |
| Opus 5 | $0.01973 | $0.01973 |
| Sonnet 5 | $0.00789 | $0.00789 |
| Haiku 4.5 | $0.00395 | $0.00395 |
Grade A, and why
freek.dev 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 3d 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When i ask you to deploy, you should execute
- commit: to commit stuff
- push: to push the github
- deploy-code: to deploy the current main branch to production
When I ask for a performance report, use the Flare skill
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.2
- filament/filament (FILAMENT) - v5
- laravel/framework (LARAVEL) - v12
- laravel/horizon (HORIZON) - v5
- laravel/mcp (MCP) - v0
- laravel/prompts (PROMPTS) - v0
- laravel/sanctum (SANCTUM) - v4
- livewire/livewire (LIVEWIRE) - v4
- pestphp/pest (PEST) - v4
- phpunit/phpunit (PHPUNIT) - v12
- prettier (PRETTIER) - v3
- tailwindcss (TAILWINDCSS) - v4
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.
livewire-development— Develops reactive Livewire 4 components. Activates when creating, updating, or modifying Livewire components; working with wire:model, wire:click, wire:loading, or any wire: directives; adding real-time updates, loading states, or reactivity; debugging component behavior; writing Livewire tests; or when the user mentions Livewire, component, counter, or reactive UI.pest-testing— Tests applications using the Pest 4 PHP framework. Activates when writing tests, creating unit or feature tests, adding assertions, testing Livewire components, browser testing, debugging test failures, working with datasets or mocking; or when the user mentions test, spec, TDD, expects, assertion, coverage, or needs to verify functionality works.tailwindcss-development— Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes.debugging-output-and-previewing-html-using-ray— Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
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.
- 3d ago First seen · 386 lines · 3,946 tokens per session scan A 1705be4c81bb
freek.dev CLAUDE.md is an instructions file published in the GitHub repository spatie/freek.dev (652 stars, last pushed 27d ago), licensed MIT. It adds 3,946 tokens to every session, about $0.0197 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.
Other instructions, from other repositories
slate AGENTS.md
AGENTS.md instructions for electrikhq/slate, covering electrik slate — agent notes, stack, install reminder, authoring rules and ai sources.
webservice AGENTS.md
AGENTS.md instructions for trakli/webservice, covering agents.md, about trakli, rule: public content, rule: support trakli and rule: api responses use one envelope.
laravel-vue-starter AGENTS.md
AGENTS.md instructions for gdarko/laravel-vue-starter, covering laravel boost guidelines, foundational context, skills activation, conventions and verification scripts.
laravel-vue-starter GEMINI.md
Gemini CLI instructions for gdarko/laravel-vue-starter, covering laravel boost guidelines, foundational context, skills activation, conventions and verification scripts.
laravel-vue-starter CLAUDE.md
Claude Code instructions for gdarko/laravel-vue-starter, covering claude.md, project overview, development commands, install and setup.
awesome-copilot copilot-instructions.md
Copilot instructions for github/awesome-copilot, covering readme updates, prompt file guide, instruction file guide, agent file guide and agent skills guide.