What is yaffa AGENTS.md?

A repository instruction file for the Yaffa Laravel application. It tells coding agents about the app's framework versions, coding conventions, architecture, and verification commands.

Use it when asking an agent to modify, review, or verify Yaffa code. It helps with Laravel and PHP work, reusing existing components, and running the project's checks.

It gives an agent the project context and local rules needed to make changes that fit the existing code. It also reduces mistakes caused by assuming the wrong package versions or file patterns.

How kantorge/yaffa configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to kantorge/yaffa. 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/kantorge/yaffa/develop/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/kantorge/yaffa

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/kantorge/yaffa/agents-md/github.svg)](https://agentmods.dev/instructions/kantorge/yaffa/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/kantorge/yaffa/agents-md"><img src="https://agentmods.dev/badge/instructions/kantorge/yaffa/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/kantorge/yaffa/agents-md"><img src="https://agentmods.dev/badge/instructions/kantorge/yaffa/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,217 This file is loaded in full into every session.

When invoked 2,217 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.

Model	Per session	Once invoked
Fable 5.1	$0.02217	$0.02217
Opus 5.5	$0.00887	$0.00887
Sonnet 5.5	$0.00443	$0.00443
Haiku 4.5	$0.00222	$0.00222

Measured today against content hash 56875adcc181, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

yaffa AGENTS.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 today.

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.

AGENTS.md · 176 lines

How it starts

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

Laravel Boost Guidelines

Foundational Context

This application is a Laravel application running on PHP 8.4. Always use the APIs that match the installed major version of each package — do not assume a version.

Before relying on a package's API, confirm its installed version:

PHP packages: run vendor/bin/sail composer show --direct to list direct dependencies with versions, or vendor/bin/sail composer show <vendor/package> for a single package.
JS packages: check package.json for the installed versions.

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.

Verification Scripts

Do not create verification scripts or tinker when tests cover that functionality and prove they work. Unit and feature tests are more important.

Application Structure & Architecture

Stick to existing directory structure; don't create new base folders without approval.
Do not change the application's dependencies without approval.

Frontend Bundling

If a frontend change doesn't show in the UI or you get a "Unable to locate file in Vite manifest" error, run vendor/bin/sail npm run build or ask the user to run vendor/bin/sail npm run dev or vendor/bin/sail composer run dev.

Documentation Files

You must only create documentation files if explicitly requested by the user.

=== boost rules ===

Laravel Boost

Tools

Laravel Boost is an MCP server with tools designed specifically for this application. Prefer Boost tools over manual alternatives like shell commands or file reads.
Use database-query to run read-only queries against the database instead of writing raw SQL in tinker.
Use database-schema to inspect table structure before writing migrations or models.
Use get-absolute-url to resolve the correct scheme, domain, and port for project URLs. Always use this before sharing a URL with the user.
Use browser-logs to read browser logs, errors, and exceptions. Only recent logs are useful, ignore old entries.

Read the full file on GitHub · 176 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.

today Changed · -13 lines · -370 tokens per session 56875adcc181
11d ago First seen · 189 lines · 2,587 tokens per session scan A e0175cbf2efe

Subscribe to this mod's changes

yaffa AGENTS.md is an instructions file published in the GitHub repository kantorge/yaffa (113 stars, last pushed today), licensed MIT. It adds 2,217 tokens to every session, about $0.0089 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-10-26.

Backend and APIs Languages PHP

yaffa AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
yaffa AGENTS.mdkantorge/yaffa	Instructions file	113	today	MIT	A	2,217	Codex, OpenCode
graftcode graftcode-php.instructions.mdgrft-dev/graftcode	Instructions file	967	1mo ago	none	A	4,619	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot

yaffa: Instructions file for Codex