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/loosewiredev/mealforge/agents-mdgit clone --depth 1 https://github.com/LooseWireDev/mealforgeWrote 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/loosewiredev/mealforge/agents-md)<a href="https://agentmods.dev/instructions/loosewiredev/mealforge/agents-md"><img src="https://agentmods.dev/badge/instructions/loosewiredev/mealforge/agents-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.01069 | $0.01069 |
| Opus 5 | $0.00535 | $0.00535 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
mealforge 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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Workflow & Project Conventions
You are a software engineer working in this monorepo. Follow the rules below. For app-specific conventions, read the per-app AGENTS.md files — they are hoisted into your context alongside this one.
Per-app context
apps/api/AGENTS.md— backend conventions (Hono + tRPC + Drizzle + SQLite; also serves the MCP endpoint and the built web app)apps/web/AGENTS.md— web app conventions (React + Vite + TanStack Router + Tailwind)
Each app's AGENTS.md describes its layout, run/test commands, and framework-specific rules.
Spec-Driven Development
- Always ask for a spec before implementing a feature.
- Session 1: Write failing tests from the spec. Do not implement.
- Session 2: Implement the minimum code to make tests pass.
- If you see implementation before tests exist, stop and ask for the spec.
Feature Development
- Always use
nx generate @mealforge/project-plugin:feature --name <name> --apps <apps>before writing feature code. - Feature names are camelCase identifiers (
userProfile, notuser-profile). - Never create feature directories manually.
- The feature generator creates the correct file structure, imports, and wiring — including registering the tRPC router in
apps/api/src/trpc.ts.
Task Execution
- Use
nx affectedto run only what changed. - Use
nx run <app>:<task>for specific apps. - Use
nx run-many --target=<task>when you need to run across all apps.
Language & Runtime
TypeScript everywhere, on Node. Not Bun, not Deno. All code is ESM. No CommonJS.
File Naming
- camelCase for all files:
userService.ts,createPost.ts,authMiddleware.ts - React components use PascalCase:
UserProfile.tsx,DashboardLayout.tsx - Test files sit next to what they test:
userService.test.tsalongsideuserService.ts - No
index.tsbarrel files insideapps/directories. Only at package boundaries (packages/shared/index.ts).
Exports
- Default exports for React components only.
- Named exports for everything else: services, utilities, hooks, types, constants.
- Every exported function has an explicit return type annotation. No exceptions.
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.
- 4d ago First seen · 111 lines · 1,069 tokens per session scan A cc117d31cb21
mealforge AGENTS.md is an instructions file published in the GitHub repository LooseWireDev/mealforge (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,069 tokens to every session, about $0.0053 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
homelab-mcp CLAUDE.md
Instructions for bjeans/homelab-mcp, covering claude development guide for homelab mcp, project overview, core philosophy, project structure and architecture patterns.
DirForge CLAUDE.md
Instructions for Dissimilis/DirForge, covering claude.md, project, philosophy, 1) security before features and 2) read-only means read-only.
selfhost-ai CLAUDE.md
Claude Code instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
homelab-monitor CLAUDE.md
Claude Code instructions for SikamikanikoBG/homelab-monitor, covering claude.md and conventions.
better-notion-mcp CLAUDE.md
Claude Code instructions for n24q02m/better-notion-mcp, covering better-notion-mcp, cau truc, lenh thuong dung, test don le and mise shortcuts.
better-notion-mcp AGENTS.md
AGENTS.md instructions for n24q02m/better-notion-mcp, covering agents.md - better-notion-mcp, build / lint / test commands, run a single test file, run a single test by name and mise shortcuts.