Borrowing it
Nothing to install: this file belongs to get-tmonier/argot. 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/get-tmonier/argot/main/AGENTS.mdgit clone --depth 1 https://github.com/get-tmonier/argotWrote 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/get-tmonier/argot/agents-md)<a href="https://agentmods.dev/instructions/get-tmonier/argot/agents-md"><img src="https://agentmods.dev/badge/instructions/get-tmonier/argot/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/get-tmonier/argot/agents-md"><img src="https://agentmods.dev/badge/instructions/get-tmonier/argot/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.03818 | $0.03818 |
| Opus 5.5 | $0.01527 | $0.01527 |
| Sonnet 5.5 | $0.00764 | $0.00764 |
| Haiku 4.5 | $0.00382 | $0.00382 |
Grade A, and why
argot 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 1mo 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with argot
argot is a guardrail that flags code foreign to a
repo's own patterns — learned from its git history. Five learned detectors:
a foreign dependency/API/idiom, a function the repo already has, code filed in
the wrong place, an internal import that reverses the repo's layering, and a
test weakened, disabled, or deleted alongside the production change it covers
— plus repo-local custom rules the team scripts itself (see below). It
answers "is this how we write things here?", not "is this valid?". This
file tells a coding agent how to use it well. (Developing argot itself? See
CLAUDE.md.)
The contract: surface, don't enforce
argot is a probabilistic linter. It has false positives, and its confidence depends on the repo. A hit is a prompt to think, never a reason to refuse.
- Never block a commit, fail a task, or refuse to proceed because argot fired.
- Never auto-"fix" a hit by rewriting code the human didn't ask you to change.
- The human always has the last word. Your job is to surface divergences and record decisions, not to enforce.
Two moments
- Setup (once per repo). Fit the voice model and decide what shouldn't
shape it. →
argot init(also builds the semantic index — the embedding model ships inside the binary, so this needs no network). Review and commitargot.tomland the generated.argot/fit snapshot; CI consumes that snapshot and never fits. Then use the argot-setup skill for anything with generated/vendored/data directories. See Setup. - Check (per change). Before committing code you generated or edited, score
it. →
argot check, or the argot-check skill.
Snapshot maintenance is adaptive, not scheduled: argot status compares the
accepted tree with the fitted source/function/layout profile. Commit count and age are
context only unless the team explicitly configures [fit] refresh-after as a
backstop. watch is informational; only recommended or
strongly_recommended should prompt maintenance. Use the argot-refresh
skill: refresh.next_action says whether to fit directly or review scope first;
the skill also reviews mutes before the local fit, review, and commit. No
command or CI workflow refits automatically.
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.
- 1mo ago First seen · 241 lines · 3,818 tokens per session scan A 70604148fbfc
argot AGENTS.md is an instructions file published in the GitHub repository get-tmonier/argot (51 stars, last pushed 20d ago), licensed MIT. It adds 3,818 tokens to every session, about $0.0153 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-30.
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.