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/mislavjc/stoop/agents-mdgit clone --depth 1 https://github.com/mislavjc/stoopWhat 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.00239 | $0.00239 |
| Opus 5 | $0.00120 | $0.00120 |
| Sonnet 5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
stoop 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.
This is a copy
95% identical to core AGENTS.md — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Release workflow
This repository uses Tegami for versioning and publishing.
Write changelog files
Create pending changelog files under .tegami/ as YYYY-MM-DD-{hash}.md.
See the changelog format docs for details.
Example
---
packages:
"npm:@acme/ui": patch
---
### Fix button hover state
The hover color now matches the design system.
Package references
Use package names, ids, or groups in frontmatter. For example:
"@acme/ui"— package name"npm:@acme/ui"— package id"group:acme"— every package in a group
Rules:
- Include YAML frontmatter with
packages - Include at least one
#,##, or###heading in the body - Write user-facing release notes under each heading
- Do not edit the publish lock file (
.tegami/publish-lock.yaml) or packageCHANGELOG.mdfiles directly
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 · 38 lines · 239 tokens per session scan A 9c42f1c851e6
stoop AGENTS.md is an instructions file published in the GitHub repository mislavjc/stoop (2 stars, last pushed 1mo ago), licensed MIT. It adds 239 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to core AGENTS.md, differing in 4 lines, and is treated as a copy.
Other instructions, from other repositories
munkel CLAUDE.md
Instructions for limehq/munkel, covering claude.md, monorepo layout, commands, macos development specifics and deploy.
vibesdk AGENTS.md
AGENTS.md instructions for cloudflare/vibesdk, covering agents.md, tooling, verification, frontend ui and frontend data fetching.
vibesdk CLAUDE.md
Claude Code instructions for cloudflare/vibesdk, covering claude.md, communication style, project overview, key architectural patterns and common development tasks.
cloudbox AGENTS.md
Instructions for acoyfellow/cloudbox, covering cloudbox agent guide, canonical commands, deploy model, cloudflare account boundaries and required production secrets.
titen AGENTS.md
Instructions for RamaAditya49/titen, covering agents.md, product, repository stage, required work lifecycle and coding constraints.
ctxlayer CLAUDE.md
Instructions for stevenn/ctxlayer, covering ctxlayer — claude code briefing, what runs where, architecture pointers, how a claude session should work in this repo and conventions.