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/vercel/eve/agents-mdgit clone --depth 1 https://github.com/vercel/eveWhat 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.03022 | $0.03022 |
| Opus 5 | $0.01511 | $0.01511 |
| Sonnet 5 | $0.00604 | $0.00604 |
| Haiku 4.5 | $0.00302 | $0.00302 |
Grade A, and why
eve 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for coding agents (and humans) working in this repository. For setup, PR workflow, and release process, see CONTRIBUTING.md.
About eve
eve is a filesystem-first framework for durable backend AI agents. You author
an agent as a directory on disk — instructions, skills, tools, connections,
channels, subagents, and schedules are all files — and eve compiles and runs it.
See the README for the full overview and
docs/ for user-facing documentation.
Always style the framework name as eve, lowercase, in user-facing copy,
docs, prompts, comments, and headings.
Repository layout
packages/eve— the framework andeveCLI (the main package)packages/eve-catalog— internal, unpublished libraryapps/fixtures— shared agent fixtures used by e2e, TUI smoke tests, and local devapps/frameworks,apps/templates,apps/docs— framework integrations, templates, docs sitedocs— published documentation contente2e/— fixture-ownedeve evalend-to-end testsresearch— issue-backed implementation plans for proposed changes
Git workflow
Commits must be cryptographically signed with a GitHub-verified key and include
the DCO Signed-off-by trailer. Use git commit -s for every commit, and if a
commit is missing the trailer, amend it with git commit --amend -s --no-edit
before pushing.
PR descriptions are reviewer-oriented explanations of the problem, solution,
meaningful behavior changes, and validation—not file lists or commit logs. Keep
them proportional to the change, link a prior issue or discussion when one
exists, call out important scope boundaries or preserved behavior, and report
only checks actually run. Never create an issue solely to accompany a PR. Use the
gh-pr-description skill when
drafting or updating one.
Commands
pnpm install # install workspace dependencies
pnpm build # build all packages
pnpm dev # watch-mode build + weather fixture on an available local port
pnpm typecheck # TypeScript across the workspace
pnpm lint # oxlint (auto-fixes)
pnpm fmt # oxfmt
pnpm guard:invariants # mechanical code-invariant checks (runs in CI)
pnpm docs:check # docs frontmatter and nav validation
pnpm test # unit + integration
pnpm test:unit # unit tests (<3s)
pnpm test:integration # integration tests (<10s)
pnpm test:scenario # scenario tests (2–5 min; requires pnpm build first)
pnpm test:e2e # fixture-owned eve eval suites (CI only)
pnpm test:tui # TUI smoke scripts (not e2e)
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 · 263 lines · 3,022 tokens per session scan A 443850c03b3e
eve AGENTS.md is an instructions file published in the GitHub repository vercel/eve (4,875 stars, last pushed 2d ago), licensed Apache-2.0. It adds 3,022 tokens to every session, about $0.0151 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
crust AGENTS.md
Instructions for chenxin-yan/crust, covering tests, documentation, changesets, agent skills and issue tracker.
page-agent AGENTS.md
AGENTS.md instructions for alibaba/page-agent, covering instructions for coding assistants, project overview, development commands, architecture and monorepo structure.
frontmcp CLAUDE.md
Instructions for agentfront/frontmcp, covering skills and tools, documentation site layout, frontmcp monorepo - development guide, repository structure and primary libraries (scoped under @frontmcp/).
frontmcp AGENTS.md
Instructions for agentfront/frontmcp, a project described as: TypeScript-first framework for the Model Context Protocol (MCP). You write clean, typed code; FrontMCP handles the protocol, transport, DI, session/auth, and execution flow.
page-agent CLAUDE.md
Claude Code instructions for alibaba/page-agent, a project described as: JavaScript in-page GUI agent. Control web interfaces with natural language.
open-code-review AGENTS.md
Instructions for alibaba/open-code-review, covering agent guidelines for open-code-review, project overview, git commit notes, license headers and code style.