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/proma-ai/proma/agents-mdgit clone --depth 1 https://github.com/proma-ai/PromaWrote 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/proma-ai/proma/agents-md)<a href="https://agentmods.dev/instructions/proma-ai/proma/agents-md"><img src="https://agentmods.dev/badge/instructions/proma-ai/proma/agents-md.svg" alt="Measured on agentmods" 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 | $0.01099 | $0.01099 |
| Opus 5 | $0.00549 | $0.00549 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
Proma 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 4d 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.
- 4d ago First seen · 80 lines · 1,099 tokens per session scan A 69eaf3398cb6
Proma AGENTS.md is an instructions file published in the GitHub repository proma-ai/Proma (2,147 stars, last pushed yesterday), licensed AGPL-3.0. It adds 1,099 tokens to every session, about $0.0055 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
lume AGENTS.md
Instructions for CavinHuang/lume, covering working agreements, 改动工作流, format, gitmoji reference and rules.
lume CLAUDE.md
Instructions for CavinHuang/lume, covering claude.md, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
AstrBot AGENTS.md
AGENTS.md instructions for AstrBotDevs/AstrBot, covering setup commands, core, dashboard(webui), pre-commit setup and dev environment tips.
dsh-chat-import AGENTS.md
Instructions for Nwflower/dsh-chat-import, covering agents.md, 背景, 命令, 仓库布局 and 编码.
skill-based-architecture AGENTS.md
Instructions for WoJiSama/skill-based-architecture, covering agents.md, quick routing (survives context truncation), auto-triggers and red flags — stop.
octo-agent CLAUDE.md
Claude Code instructions for open-octo/octo-agent, covering claude.md, project, commands, architecture and adding capability.