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/yeet-src/agent-lock/agents-mdgit clone --depth 1 https://github.com/yeet-src/agent-lockWhat 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.07310 | $0.07310 |
| Opus 5 | $0.03655 | $0.03655 |
| Sonnet 5 | $0.01462 | $0.01462 |
| Haiku 4.5 | $0.00731 | $0.00731 |
Grade A, and why
agent-lock 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 2d 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.
The source is not reproduced here
Licensed GPL-2.0
The repository is licensed GPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 696 lines · 7,310 tokens per session scan A 092a7ef8ba6c
agent-lock AGENTS.md is an instructions file published in the GitHub repository yeet-src/agent-lock (39 stars, last pushed 12d ago), licensed GPL-2.0. It adds 7,310 tokens to every session, about $0.0365 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-30.
Other instructions, from other repositories
schedcp CLAUDE.md
Instructions for eunomia-bpf/schedcp, covering claude.md, project overview, essential build commands, building the mcp server and cli and build the schedcp mcp server and cli tool.
agent-jail AGENTS.md
AGENTS.md instructions for yeet-src/agent-jail, covering building yeet dashboards, mental model, build bottom-up: data → component → layout, 1. get the data right first, in isolation and 2. build each component against a fake signal.
mcp-ssh GEMINI.md
Gemini CLI instructions for zhouxiangjing/mcp-ssh, covering ssh mcp server — ai agent guide, role activation — read this first, critical: mcp trigger policy, tool groups & trigger conditions and 1. connection management.
Sponsio CLAUDE.md
Instructions for SponsioLabs/Sponsio, covering agent guide for sponsio, what sponsio is, positioning, what to read first and repository map.
best-claude-hud AGENTS.md
Instructions for GaoSSR/best-claude-hud, covering project agent instructions and release work.
caracal console-example-naming.instructions.md
Use when writing, editing, or reviewing web console help, info pages, field examples, guided setup copy, or example-facing web console UI text. Enforces the approved Caracal demo naming universe.