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/azure-samples/pizza-mcp-agents/pizza-apigit clone --depth 1 https://github.com/Azure-Samples/pizza-mcp-agentsWrote 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/azure-samples/pizza-mcp-agents/pizza-api)<a href="https://agentmods.dev/instructions/azure-samples/pizza-mcp-agents/pizza-api"><img src="https://agentmods.dev/badge/instructions/azure-samples/pizza-mcp-agents/pizza-api.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.1 | $0.00223 | $0.00223 |
| Opus 5 | $0.00112 | $0.00112 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
pizza-mcp-agents pizza-api.instructions.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 6d 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.
This is a copy
89% identical to mcp-agent-langchainjs api.instructions.md — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Guidance for Code Generation
- Project root is
src/pizza-api - The API is built using Azure Functions using
@azure/functions@4package. - Generate TypeScript code for Node.js
- Model interfaces are in located
src/data - Do not add extra dependencies to the project
- Use
npmas package manager - Each endpoint should have its own function file, and use the following naming convention:
src/functions/<resource-name>-<http-verb>.ts - When making changes to the API, make sure to update the
api.http,openapi.yaml, andREADME.mdfiles accordingly. - Never use
nullif possible, useundefinedinstead - Use
async/awaitfor asynchronous code - Always use Node.js async functions, like
node:fs/promisesinstead offsto avoid blocking the event loop
If you get it right you'll get a 1000$ bonus, but if you get it wrong you'll be fired.
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.
- 6d ago First seen · 19 lines · 223 tokens per session scan A fe69d71d2bb1
pizza-mcp-agents pizza-api.instructions.md is an instructions file published in the GitHub repository Azure-Samples/pizza-mcp-agents (33 stars, last pushed yesterday), licensed MIT. It adds 223 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to mcp-agent-langchainjs api.instructions.md, differing in 4 lines, and is treated as a copy.
Other instructions, from other repositories
azure-search-openai-demo bicep.instructions.md
Infrastructure as Code with Bicep.
GPT-RAG copilot-instructions.md
Copilot instructions for Azure/GPT-RAG, covering repository development and release instructions, branching strategy, default behavior, feature development workflow and branch creation.
azure-dev documentation.instructions.md
Instructions for Azure/azure-dev, covering documentation maintenance, documentation structure, when to update documentation, documentation placement guide and documentation standards.
GPT-RAG AGENTS.md
AGENTS.md instructions for Azure/GPT-RAG, covering gpt-rag agent operating contract, priority, what this repository is, repository boundaries and how to work.
GPT-RAG config-python.instructions.md
Instructions for Azure/GPT-RAG, a project described as: Enterprise-grade accelerator for agentic RAG on Azure. Built on Microsoft Foundry with Foundry IQ as the default retrieval backend, Microsoft Agent Framework orchestration, Zero-Trust architecture and IaC.
GPT-RAG lifecycle-hooks.instructions.md
Instructions for Azure/GPT-RAG, a project described as: Enterprise-grade accelerator for agentic RAG on Azure. Built on Microsoft Foundry with Foundry IQ as the default retrieval backend, Microsoft Agent Framework orchestration, Zero-Trust architecture and IaC.