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/jirathip-dev/morsel/claude-mdgit clone --depth 1 https://github.com/jirathip-dev/morselWrote 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/jirathip-dev/morsel/claude-md)<a href="https://agentmods.dev/instructions/jirathip-dev/morsel/claude-md"><img src="https://agentmods.dev/badge/instructions/jirathip-dev/morsel/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.00385 | $0.00385 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
morsel 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 2d 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.
What it actually says
AGENTS.md — context for agents working in this repo
What this project is
Morsel is an MCP-first, camera-first food tracker. The product is a data store + dashboard + agent skill; there is no in-app chat and no in-app AI. The user logs by chatting with Claude/ChatGPT and uploading a food photo; the assistant's agent calls Morsel's MCP tools to write structured nutrition data.
Where the source of truth lives
- The tool contract =
docs/MCP_TOOLS.mdandpackages/schema/food-types.ts. When the contract changes, edit the schema FIRST; the server and the agent skill derive from it. Do not hand-edit tool implementations until they drift. - The data model =
db/migrations/*.sql(canonical) +docs/DATA_MODEL.md. - Architecture =
docs/ARCHITECTURE.md.
Conventions
- Server = Bun + Hono + MCP SDK over streamable HTTP. App = SwiftUI. Store = Supabase: Postgres + Auth + RLS + Storage (food images).
- Every table is user-scoped and guarded by RLS (
auth.uid() = user_id). The MCP server authenticates with the user's access token so policies apply. - Keep the tool set small and talkative: agents work better with clear, few tools than many overlapping ones.
- A feature is not done until all three describe it: the MCP tool schema, the agent skill, and the dashboard rendering what it produced.
Rules
- Never publish, push, or open issues/PRs without explicit human approval.
- Read
docs/DATA_MODEL.mdanddocs/MCP_TOOLS.mdbefore writing any code.
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.
- 2d ago First seen · 29 lines · 385 tokens per session scan A a7a41b12ac77
morsel CLAUDE.md is an instructions file published in the GitHub repository jirathip-dev/morsel (0 stars, last pushed 2d ago), licensed MIT. It adds 385 tokens to every session, about $0.0019 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.