agentmods.dev

WhatToEatNext: Instructions file for Claude Code

CLAUDE.md

WhatToEatNext CLAUDE.md is an instructions file for Claude Code from gregcastro23/WhatToEatNext. It costs 548 tokens per session, scanned A, original, MIT.

A repository instruction file for WhatToEatNext, describing its build, test, issue-tracking, domain-documentation, and administrator-interface rules. It tells coding agents how to work in that project.

In plain words
What is it for?
It is for guiding builds, type checks, tests, issue triage, domain documentation, and changes to the admin pages.
Why use it?
It keeps agent changes aligned with the repository's required commands, GitHub issue process, data-source rules, and access controls.

Instructions file for Claude Code

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

This is gregcastro23/WhatToEatNext's own configuration. It tells Claude Code how to work on WhatToEatNext 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 WhatToEatNext configures →

not rated 0repo today A scan 548 tokens original MIT
View source ↗ gregcastro23/WhatToEatNext v0-alchm-kitchen.vercel.app
Reuse

Borrowing it

Nothing to install: this file belongs to gregcastro23/WhatToEatNext. 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/gregcastro23/WhatToEatNext/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/gregcastro23/WhatToEatNext

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 WhatToEatNext CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gregcastro23/whattoeatnext/claude-md.svg)](https://agentmods.dev/instructions/gregcastro23/whattoeatnext/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/gregcastro23/whattoeatnext/claude-md"><img src="https://agentmods.dev/badge/instructions/gregcastro23/whattoeatnext/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 548 This file is loaded in full into every session.
When invoked 548 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.00548 $0.00548
Opus 5 $0.00274 $0.00274
Sonnet 5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

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

Security

Grade A, and why

WhatToEatNext 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 7d 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 · 34 lines

How it starts

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

WhatToEatNext - Agent Guidance

Build and Test Commands

  • Build: bun run build
  • Typecheck: bun run typecheck
  • Verify: bun run verify
  • Test: bun run test

Agent skills

Issue tracker

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations. Pull requests are not a request surface for triage. See docs/agents/issue-tracker.md.

Triage labels

The five canonical triage states are mapped 1-to-1 to the labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See docs/agents/triage-labels.md.

Domain docs

Uses a single-context domain model layout with CONTEXT.md at the root and ADRs in docs/adr/. See docs/agents/domain.md.

Admin surface

Operator UI lives under src/app/admin/* behind the sidebar in admin/layout.tsx (admin-role + isAdminEmail gated). Every panel reads a live source — never fabricate admin data; degrade to an honest live: false/"no source" state instead.

  • Overview (/admin) — panels in src/components/admin/*Panel.tsx, each self-polling via useHardenedPolling. Top of page is LaunchReadinessPanel (settlement backlog + config health).
  • Dashboard ✦ (/admin/dashboard) — the "High Alchemist" full-bleed board in src/app/admin/_dashboard/, fed entirely by GET /api/admin/dashboard → AdminDashboardData.
  • Settlements (/admin/settlements) — restaurant ESMS settlement handle (retry/refund stuck crypto-food orders); GET/POST /api/admin/restaurants/settlement. Required before public payments launch (docs/payments/CRYPTO_FOOD_PAYMENTS.md).
  • Moderation — /admin/chat-reports (/api/admin/chat/reports) and /admin/feed/comment-reports.
  • Settings (/admin/settings) — live launch-readiness board over static platform facts.

Launch readiness = presence-only env config for the revenue/on-chain subsystems (Stripe, restaurant crypto-food payments, on-chain ESMS, Recipe-NFT, Privy, Amazon Fresh, agent network, email). Source: src/services/launchReadinessService.ts → GET /api/admin/launch-readiness. It reports booleans only — never serialize a secret's value.

Read the full file on GitHub · 34 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. 7d ago First seen · 34 lines · 548 tokens per session scan A f25aa6120972

Subscribe to this mod's changes

WhatToEatNext CLAUDE.md is an instructions file published in the GitHub repository gregcastro23/WhatToEatNext (0 stars, last pushed today), licensed MIT. It adds 548 tokens to every session, about $0.0027 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

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