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/fmind/agent-evolutions/gemini-mdgit clone --depth 1 https://github.com/fmind/agent-evolutionsWhat 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.00005 | $0.00005 |
| Opus 5 | $0.00003 | $0.00003 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00001 | $0.00001 |
Grade A, and why
agent-evolutions GEMINI.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 yesterday.
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.
This is a copy
100% identical to deepseek-harness CLAUDE.md — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
@AGENTS.md
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.
- yesterday First seen · 2 lines · 5 tokens per session scan A 336cc4fbf19b
agent-evolutions GEMINI.md is an instructions file published in the GitHub repository fmind/agent-evolutions (1 stars, last pushed 3mo ago), licensed MIT. It adds 5 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 3 lines, and is treated as a copy.
Other instructions, from other repositories
eai-gofer copilot-instructions.md
Copilot instructions for eai-support/eai-gofer, covering copilot instructions, project overview, gofer pipeline, token and cost policy and code quality.
eai-gofer language-server.instructions.md
Instructions for eai-support/eai-gofer, covering language server development instructions, architecture, key files, mcp tools (6 total) and adding new mcp tools.
eai-gofer typescript.instructions.md
Instructions for eai-support/eai-gofer, covering typescript development instructions, code quality standards, file structure and testing.
eai-gofer vscode-extension.instructions.md
Instructions for eai-support/eai-gofer, covering vscode extension development instructions, key architecture, vscode apis to use, important patterns and testing.
eai-gofer gofer-cost.instructions.md
Instructions for eai-support/eai-gofer: Before running Gofer stages, spawning agents, or loading large files.
agent-levers AGENTS.md
Instructions for fmind/agent-levers, covering agents.md, conventions, workflow and layout.