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/simba87/iiko-server-mcp/agents-mdgit clone --depth 1 https://github.com/simba87/iiko-server-mcpWrote 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/simba87/iiko-server-mcp/agents-md)<a href="https://agentmods.dev/instructions/simba87/iiko-server-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/simba87/iiko-server-mcp/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.01178 | $0.01178 |
| Opus 5 | $0.00589 | $0.00589 |
| Sonnet 5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
iiko-server-mcp 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 3d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Context: iiko-server-mcp
MCP (Model Context Protocol) server that wraps the iikoServer REST API as 42+ tools over stdio.
Architecture
MCP Client (Claude/Hermes/Cursor)
└─ stdio ─► Server.__init__("iiko-server-mcp")
└─ IikoClient (httpx.AsyncClient)
└─ HTTPS ─► iikoServer REST API
- Auth: SHA1(password) →
GET /resto/api/auth?login=...&pass=...→ cookiekey - Auto re-auth: 401 triggers
_auth()retry (once) - SSL:
IIKO_VERIFY_SSL=falseby default (iiko often uses self-signed certs) - Logout: graceful
GET /resto/api/logout?key=...on shutdown
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
IIKO_URL |
yes | — | iikoServer base URL (e.g. https://your-restaurant.iiko.it:443) |
IIKO_LOGIN |
yes | — | Login username |
IIKO_PASS |
yes | — | Plain password (SHA1 hashed internally before sending) |
IIKO_VENUE_MAP |
no | — | "Name=4,Name=5" mapping of cash register numbers to venue names |
IIKO_VERIFY_SSL |
no | false |
Set to true for CA-signed certs |
Tool Categories (42+ tools)
| Category | Tools |
|---|---|
| System | ping, list_endpoints |
| Products/Nomenclature | get_products, get_product_groups, get_product_sizes, get_nomenclature, get_corporate_structure, get_corporate_groups, search_products |
| Employees | get_employees, get_employee, get_employee_roles, get_persons |
| Entities | get_entity_types, get_entities, get_entity_by_id, get_stores, get_contractors |
| Documents | get_incoming_invoices, get_outgoing_invoices, get_incoming_invoice_by_id, get_outgoing_invoice_by_id, get_waste_documents, get_menu_changes, get_menu_change_by_id |
| Recipes | get_assembly_charts, get_assembly_chart_by_id, save_assembly_chart |
| Cash & Payments | get_payment_types, get_cash_shifts, get_cash_shift, get_payments, get_payment, create_encashment |
| Prices | get_price_categories, get_price_category |
| Reports & OLAP | get_olap_columns, run_olap_report, get_olap_presets, run_olap_by_preset, run_custom_report, get_venues_revenue, get_staff_meals, get_top_dishes, compare_revenue, get_checks |
| Raw | raw_request |
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.
- 3d ago First seen · 100 lines · 1,178 tokens per session scan A 025b9e0f50f7
iiko-server-mcp AGENTS.md is an instructions file published in the GitHub repository simba87/iiko-server-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,178 tokens to every session, about $0.0059 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.