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/s2-streamstore/cachey/agents-mdgit clone --depth 1 https://github.com/s2-streamstore/cacheyWhat 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.00345 | $0.00345 |
| Opus 5 | $0.00172 | $0.00172 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
cachey 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.
What it actually says
cachey is a read-through cache for S3-compatible object storage
- NO TRIVIAL COMMENTS
- Follow Rust idioms and best practices
- Latest Rust features can be used
- Descriptive variable and function names
- No wildcard imports
- Explicit error handling with
Result<T, E>over panics - Use
eyre::Reportwhen the specific error is not as important - Use custom error types using
thiserrorfor domain-specific errors - Format:
cargo +nightly fmt - Lint:
cargo clippy --locked --all-features --all-targets -- -D warnings --allow deprecated - Dependency policy:
cargo deny check - Place unit tests in the same file using
#[cfg(test)]modules - Integration tests go in the
tests/directory - Run tests with:
cargo nextest run --locked - Use
--lockedfor Cargo commands that build, check, test, run, document, fetch, or read metadata - Use
cargo +nightly add,cargo +nightly update,cargo +nightly remove, orcargo +nightly generate-lockfilefor dependency changes - Do not use the stable forms of these dependency commands
- Do not edit dependency declarations or
Cargo.lockdirectly - Do not run
cargo installas part of a coding task - Prefer well-maintained crates from crates.io
- Be mindful of allocations in hot paths
- Prefer structured logging
- Provide helpful error messages
- Use conventional commit format for commit messages and PR titles
- PR descriptions should include
Closes #<issue>when applicable
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 · 28 lines · 345 tokens per session scan A c1a232edb9fd
cachey AGENTS.md is an instructions file published in the GitHub repository s2-streamstore/cachey (617 stars, last pushed 6d ago), licensed MIT. It adds 345 tokens to every session, about $0.0017 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.