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/beam-cloud/airstore/agents-mdgit clone --depth 1 https://github.com/beam-cloud/airstoreWhat 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.01047 | $0.01047 |
| Opus 5 | $0.00524 | $0.00524 |
| Sonnet 5 | $0.00209 | $0.00209 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
airstore 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 AGPL-3.0
The repository is licensed AGPL-3.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 · 96 lines · 1,047 tokens per session scan A d3409f4f8166
airstore AGENTS.md is an instructions file published in the GitHub repository beam-cloud/airstore (188 stars, last pushed 4mo ago), licensed AGPL-3.0. It adds 1,047 tokens to every session, about $0.0052 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
artifact-fs AGENTS.md
Instructions for cloudflare/artifact-fs, covering agents.md, code review rules, architecture, runtime contracts and code conventions.
frankenfs AGENTS.md
AGENTS.md instructions for Dicklesworthstone/frankenfs, covering agents.md — frankenfs (ffs), rule 0 - the fundamental override prerogative, rule number 1: no file deletion, git branch: only use main, never master and toolchain: rust & cargo.
autocontext CLAUDE.md
Instructions for greyhaven-ai/autocontext, covering claude.md, project overview, repository layout, commands and setup.
librefang AGENTS.md
Instructions for librefang/librefang, covering stack, layout, build, architecture and kernelhandle trait.
autonomous-os AGENTS.md
Instructions for autonomous-ai/autonomous-os, covering agents.md, multi-ide rules, working style, parallel work / subagents and device access rules.
clawmetry AGENTS.md
Instructions for vivekchand/clawmetry, covering agents.md — for ai coding agents, quick context, where new code goes (open-core split), the rules that bite and common tasks.