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/nerdconf/veta/agents-mdgit clone --depth 1 https://github.com/nerdconf/vetaWhat 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.00118 | $0.00118 |
| Opus 5 | $0.00059 | $0.00059 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
veta 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 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.
What it actually says
Veta agent instructions
When the user asks to install, sync, scrape, import, organize, or query their X
bookmarks with Veta, read and follow AGENT_INSTALL.md completely.
The user-facing contract is agent-first: use the browser already available in the current agent product. Never turn browser configuration, MCP registration, or local setup into a human onboarding checklist.
For code changes, preserve the local-only boundary. Do not add X OAuth, paid X API access, AI API-key forms, analytics, or hosted user data unless explicitly requested.
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 · 13 lines · 118 tokens per session scan A 5f7336673f08
veta AGENTS.md is an instructions file published in the GitHub repository nerdconf/veta (0 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session, about $0.0006 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
qaskills AGENTS.md
Instructions for PramodDutta/qaskills, covering agents.md, project overview, common commands, run a single package and run tests in watch mode.
agentic-playwright data-strategy.instructions.md
Instructions for idavidov13/agentic-playwright, covering data strategy, critical, file locations, instructions and phase 1: classify the value you need.
agentic-playwright config.instructions.md
Instructions for idavidov13/agentic-playwright, covering configuration, critical, file locations, instructions and phase 1: understand how env files are loaded.
agentic-playwright refactor-values.instructions.md
Instructions for idavidov13/agentic-playwright, covering refactoring enum values and static test data, critical, instructions, phase 1: find all consumers before touching anything and find all usages of the enum key.
inspecto CLAUDE.md
Instructions for inspecto-dev/inspecto, covering inspecto — claude code development guide, project overview, monorepo structure, development phases (load each file as needed) and key architectural decisions.
browser-bridge AGENTS.md
Instructions for koltyakov/browser-bridge, covering project guide, data flow, package map, where to find things and method dispatch (extension side).