Borrowing it
Nothing to install: this file belongs to ametel01/agentreceipt. 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/ametel01/agentreceipt/main/AGENTS.mdgit clone --depth 1 https://github.com/ametel01/agentreceiptWrote 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/ametel01/agentreceipt/agents-md)<a href="https://agentmods.dev/instructions/ametel01/agentreceipt/agents-md"><img src="https://agentmods.dev/badge/instructions/ametel01/agentreceipt/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/ametel01/agentreceipt/agents-md"><img src="https://agentmods.dev/badge/instructions/ametel01/agentreceipt/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.00572 | $0.00572 |
| Opus 5.5 | $0.00229 | $0.00229 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
agentreceipt 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentReceipt repository instructions
Instruction version
This checked-in AGENTS.md is the canonical instruction file for the Agent Learning Loop pilot. AgentReceipt captures its repository-relative path and SHA-256 content hash when each Pilot Task starts. Do not edit this file while collecting a baseline cohort; a change creates a new instruction version and closes the current cohort.
Pilot baseline capture
Before the first substantive edit of an enrolled Pilot Task:
-
Run
agentreceipt startto start one non-blocking AgentReceipt capture for the task and keep it active through final validation or abandonment. -
Add one signed enrollment marker with this exact, privacy-safe shape:
pilot_phase=baseline task_id=<repo-local-id> task_type=<feature|bug-fix|refactor|test|documentation|ci|maintenance> intended_surface=<production|tests|documentation|configuration-ci|dependencies> planned_complexity=<small|medium|large> delivery_path=<pr|direct-commit> proposal=none -
Run
agentreceipt statusand requireState: active,- git: active, and- filesystem: activebefore editing. -
If the status gate fails, do not edit. Repair capture under the same task ID and rerun the gate. If repair requires a new capture, repeat the signed marker with the same task ID; group all resulting receipts into one Pilot Observation. Count one enrollment miss only if the Pilot Task never yields an Eligible Receipt.
-
Use
agentreceipt start --watchonly as an optional live view in a second terminal.agentreceipt stopimports matching Codex Provider Evidence before finalization; unavailable Provider Evidence remains a gap rather than an automatic exclusion. -
Do not put task descriptions, prompts, personal data, secrets, absolute paths, or raw provider output in the marker.
-
Stop and finalize the capture only after validation, abandonment, or an explicit rejection.
The pilot ledger records the receipt ID or hash, instruction-file hash, normalized provider and filesystem evidence, and manually adjudicated downstream result. Receipts and replay bundles stay local; only privacy-reviewed IDs, hashes, aggregate measurements, findings, decisions, and reviewed repository changes may be committed or posted.
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 · 41 lines · 572 tokens per session scan A 09a136caa89b
agentreceipt AGENTS.md is an instructions file published in the GitHub repository ametel01/agentreceipt (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 572 tokens to every session, about $0.0023 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.