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/dmtrkovalenko/fff/agents-mdgit clone --depth 1 https://github.com/dmtrKovalenko/fffWhat 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.01321 | $0.01321 |
| Opus 5 | $0.00660 | $0.00660 |
| Sonnet 5 | $0.00264 | $0.00264 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
fff 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Clankers
This repository contains FFF.nvim (Fast File Finder), a high-performance file picker for Neovim inspired by blink.cmp's fuzzy matching technology. It's NOT a completion plugin, but rather a standalone file finder with advanced fuzzy search and frecency scoring. The project aims to be the drop-in replacement for telescope, fzf-lua, snacks.picker and similar plugins, focusing on speed, accuracy search and usability features.
Development Commands
Always prefer Makefile commands listed to the cargo/bun/node if possible.
Building
make build- build everything
Testing and Development Tools
This project does not have a traditional test suite. Testing is done through:
- Create e2e local test file for Neovim: Load any Lua test file with
nvim -l <test_file> - Write inline rust unit tests for any functionality that is standalone and scoped within a single function
Code Quality
make lint- Rust linting and code analysismake format- Format all codemake test- Run unit tests (limited coverage, primarily integration testing)
When doing code make sure to REDUCE SIZE OF COMMENTS. This is very important. Every comment should be concise 1-2 liner maximum 4 lines if describes really extensive and unnatural concept.
Important coding rules
- Do not add doc comments to the private structs and functions.
- Do not make public structs if something can be private
Style guide
- NO MODULES COMMENTS
- NO TOP FILE COMMENTS
- NO COMMENT LONGER THAN 2 LINES UNLESS ASKED EXPLICITLY
- UTILITY FUNCTIONS GO INTO THE END OF FILE
Architecture
Everything that is performance critical happens in rust world, everything that is neovim specific happens in the lua code.
There are 3 main components:
- Rust binary with the global file picker state containing index of all files
- Background thread with the file system watcher that updates the index in real time
- Lua UI layer that renders the picker, handles user input, and calls the rust functions via FFI
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 · 119 lines · 1,321 tokens per session scan A bf506bb095f4
fff AGENTS.md is an instructions file published in the GitHub repository dmtrKovalenko/fff (10,353 stars, last pushed yesterday), licensed MIT. It adds 1,321 tokens to every session, about $0.0066 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
review.nvim CLAUDE.md
Instructions for vuki656/review.nvim, covering claude.md, commands, lint, run all tests and run a single test file.
codecompanion-spinners.nvim GEMINI.md
Instructions for lalitmee/codecompanion-spinners.nvim, covering codecompanion spinner - comprehensive context, project overview, architecture, core components and event handling.
agentic.nvim AGENTS.md
Instructions for carlos-algms/agentic.nvim, covering agents guide, nested instructions, skill driven, domain glossary — lazy read and architectural decisions (adrs) — optional read.
hlchunk.nvim AGENTS.md
Instructions for shellRaining/hlchunk.nvim, covering agents.md, 项目定位, 技术栈约束, 本地命令 and 目录地图.
agentic.nvim CLAUDE.md
Instructions for carlos-algms/agentic.nvim: CRITICAL See @AGENTS.md for Instructions, it's the source of truth for all my instructions, no exceptions, it should be read and be part of your context before any other action.
sidekick.nvim AGENTS.md
Instructions for folke/sidekick.nvim, covering agent cheat sheet, project overview, everyday commands, adding features and writing tests.