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/aayushmau5/eva/agents-mdgit clone --depth 1 https://github.com/aayushmau5/evaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/aayushmau5/eva/agents-md)<a href="https://agentmods.dev/instructions/aayushmau5/eva/agents-md"><img src="https://agentmods.dev/badge/instructions/aayushmau5/eva/agents-md.svg" alt="Measured on agentmods" height="20"></a>What 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.00463 | $0.00463 |
| Opus 5 | $0.00231 | $0.00231 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
eva 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 3d 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
AGENTS.md
Before Committing / After Writing Code
Always run mix precommit after code changes are complete and before committing. This catches compile warnings, unused deps, formatting issues, and test failures in one pass.
Packages
Two Mix projects live here, and the boundary between them is a namespace:
. |
:eva |
the host — sessions, the agent loop, providers, tools, extension loading |
core/ |
:eva_core |
the contract an extension is written against |
Everything in core/ is Eva.Core.* and lives under core/lib/eva/core/. Everything in
the host is Eva.*. So Eva.Core.Bus and Eva.Core.Extension.Spec are contract;
Eva.Extension.Loader and Eva.Cluster are host. The two interleave — Eva.Agent.*,
Eva.Cluster.* and Eva.Extension.* each have modules on both sides — so when renaming or
moving anything in those trees, check which package owns it rather than matching a prefix.
The one namespace that is neither: Eva.Extension.<Name> is where an extension itself
must live (Eva.Core.Extension.namespace/1 enforces it). Third-party code, not core's.
Extensions are separate repos. MCP is at ../eva-mcp and depends on eva_core through a
sparse git checkout of core/; set EVA_CORE_PATH there to build it against a local Eva.
test/eva/mcp_node_test.exs is the only test that crosses into it, and skips if it is
absent.
Architecture
Keep modules cohesive — each module does one thing well. StreamState owns SSE buffering and delta accumulation; OpenAICompatible owns the GenServer lifecycle and HTTP streaming for Open-AI compatible APIs; Sse owns raw SSE line parsing. Don't cram unrelated concerns into one module.
Code flows through functions. Prefer Elixir's control-flow constructs — with, case, cond, Enum.reduce/3, and the pipe operator — over deeply nested if/else.
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.
- 3d ago First seen · 35 lines · 463 tokens per session scan A 59cda2d817a8
eva AGENTS.md is an instructions file published in the GitHub repository aayushmau5/eva (5 stars, last pushed 6d ago), licensed MIT. It adds 463 tokens to every session, about $0.0023 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
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).
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.
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.
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.
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).
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.