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/saltyskip/rift/agents-mdgit clone --depth 1 https://github.com/saltyskip/riftWhat 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.00793 | $0.00793 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
rift 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 61 lines · 793 tokens per session scan A ade6bc126d73
rift AGENTS.md is an instructions file published in the GitHub repository saltyskip/rift (7 stars, last pushed 2mo ago), with no licence file. It adds 793 tokens to every session, about $0.0040 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-31.
Other instructions, from other repositories
rustzen-admin AGENTS.md
Instructions for idaibin/rustzen-admin, covering repository rules, source of truth, reading order, boundaries and working rules.
smartest-tv CLAUDE.md
Instructions for Hybirdss/smartest-tv, covering smartest-tv, tech stack, commands, install and setup.
humblytics-marketing-skills AGENTS.md
Instructions for Humblytics/humblytics-marketing-skills, covering agents.md, repository purpose, security rules, skill file format and humblytics mcp.
atrib CLAUDE.md
Instructions for creatornader/atrib, covering atrib: the protocol for verifiable agent actions, what this is, repository structure, hub doc and authoritative docs.
aura-llm-gateway AGENTS.md
Instructions for UmaiTech/aura-llm-gateway, covering aura llm gateway, project overview, tech stack, project structure and development commands.
booklog CLAUDE.md
Instructions for jnsgruk/booklog, covering claude code guidelines for booklog, project overview, build & test commands, workflow requirements and architecture.