Borrowing it
Nothing to install: this file belongs to attenlabs/hotato. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/attenlabs/hotato/main/AGENTS.mdgit clone --depth 1 https://github.com/attenlabs/hotatoWrote 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/attenlabs/hotato/agents-md)<a href="https://agentmods.dev/instructions/attenlabs/hotato/agents-md"><img src="https://agentmods.dev/badge/instructions/attenlabs/hotato/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/attenlabs/hotato/agents-md"><img src="https://agentmods.dev/badge/instructions/attenlabs/hotato/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02697 | $0.02697 |
| Opus 5.5 | $0.01079 | $0.01079 |
| Sonnet 5.5 | $0.00539 | $0.00539 |
| Haiku 4.5 | $0.00270 | $0.00270 |
Grade A, and why
hotato 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 2mo 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
You are an agent evaluating or wiring up hotato, the local-first AI
engineering platform, to trace, evaluate, test, and gate an AI agent (voice,
chat, or LLM). This file is written to be executed top to bottom. Every command
below is offline, reversible, and needs no account or key. Prefer the CLI's own
contract
(hotato describe --format json) over this prose when they disagree.
The core loop (run this first)
One path, first touch to a CI gate. Each step prints the exact next command, so you can chain the whole loop from stdout alone:
1 hotato start --demo see it catch a failure on two bundled calls
2 hotato investigate ./call.wav score your own two-channel recording
3 hotato investigate label <ref> commit the caught moment as a regression
4 hotato pr create --fixtures <bundle> open the pull request that adds the CI gate
5 hotato contract verify contracts/ the gate re-runs the stored evidence
- Step 1 sweeps the two bundled demo calls, builds one failure contract, and runs one say-do conversation check. It exits 0 because setup finished; the gate command it points at exits 1.
- Step 2 opens a local dual-channel WAV (or pulls one live with
--stack vapi --call-id ID), authenticates its capture origin, runs the input-health gate, and ranks the timing moments. It marks the top-ranked onemost likely failureand prints oneinvestigate labelcommand for it. No intent is inferred; a suspected channel swap refuses the verdict path. - Step 3 writes a content-addressed contract bundle to
contracts/<id>.hotato/from the candidate ref (.hotato/investigate-state.json#N) and the--expect yield|holdlabel you supply. The label is the human decision; hotato measures whether the timing matched it. - Step 4 stages that bundle byte-identical under
tests/hotato/contracts/and opens the PR (dry run by default;--yesruns git and gh). - Step 5 re-measures the stored evidence deterministically. This is the CI gate: exit 0 pass, exit 1 fail.
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.
- 2mo ago First seen · 231 lines · 2,697 tokens per session scan A b1a2edd8a1a1
hotato AGENTS.md is an instructions file published in the GitHub repository attenlabs/hotato (2 stars, last pushed 2mo ago), licensed MIT. It adds 2,697 tokens to every session, about $0.0108 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.