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/tothalex/drift/agents-mdgit clone --depth 1 https://github.com/tothalex/driftWhat 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.01335 | $0.01335 |
| Opus 5 | $0.00668 | $0.00668 |
| Sonnet 5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
drift 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
drift — agent instructions
drift is a Rust terminal UI for reviewing working changes like a pull request: everything since the base branch (committed, uncommitted, untracked) in one live view, plus real GitHub/GitLab PR review and a send-to-AI-agent integration.
Commands
cargo build # debug binary at target/debug/drift
cargo test # unit + integration tests (tests/git_vcs.rs)
cargo test <name> # one test by substring
cargo clippy --all-targets # must be warning-free
cargo fmt # required before committing
Architecture
src/app/— the coordinator: event loop, key dispatch, overlay state (picker, compose, help). Fully synchronous — no async runtime; background work isstd::thread::spawn+ anAppEventchannel.src/lang/— the language registry: name, extensions, grammar, block kinds, highlight queries per language. Everything language- specific lives here. No grammar is compiled into drift: every language is a plugin (manifest + query + dylib-compiled grammar under the config dir'slanguages/), installed via thedrift langCLI or the in-app prompt and hot-loaded. The curated install registry is the repo'slanguages/directory (manifests + drift's query stacks), embedded into the binary — adding a curated language = one manifest file there, and tests validate every entry. Unit tests see a registry built from dev-dependency grammar crates plus those curated files, so the suite runs without git or a C compiler; the crate versions in[dev-dependencies]must match the revs the curated manifests pin.src/processor/— tree-sitter block scoping, syntax highlighting, view flattening (view.rsis the canonical row model). Language- agnostic: grammars and queries come fromsrc/lang/.src/vcs/— git via gitoxide; never shells out togit.src/forge/— PRs through the officialgh/glabCLIs; drift never speaks HTTP itself. One submodule per forge behind theForgetrait.src/connect/— send-to-agent backends behind theBridgetrait; one submodule per multiplexer plus aBACKENDSregistry table inmod.rs. Adding a backend touches only this directory: new file, newBackendvariant, one registry row.src/keymap.rs— bindings as data:KEY_DEFAULTS+HELPtables; tests enforce that every action is bound and appears in help.src/theme.rs— every color drift paints;THEME_DEFAULTSis the single source (onedark_dark palette).src/config.rs—~/.config/drift/config.toml; each section is a serde struct with aninto_config()validator, anddefault_toml()must stay parseable (a test round-trips it).
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 · 101 lines · 1,335 tokens per session scan A 48b3a8f34087
drift AGENTS.md is an instructions file published in the GitHub repository tothalex/drift (44 stars, last pushed 12d ago), licensed MIT. It adds 1,335 tokens to every session, about $0.0067 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
katamari AGENTS.md
Instructions for isamisushi/katamari, covering agents.md — working on katamari, build/test, tests, architecture pointers and style.
drip CLAUDE.md
Instructions for drip-cli/drip, covering claude.md, build, test, lint, trying a local build against a real read, benchmarks (release binary only) and repository conventions.
cli AGENTS.md
Instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.