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/claude-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.00081 | $0.00081 |
| Opus 5 | $0.00041 | $0.00041 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
veta CLAUDE.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.
What it actually says
Veta for Claude Code
For installation, X bookmark sync, import, organization, and library queries,
read and follow AGENT_INSTALL.md completely.
Use Claude Code's current browser capability and existing subscription. Do not
ask the user to configure browser tooling, an X developer account, or an AI API
key. Register Veta with npm run setup -- --agent claude.
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 · 9 lines · 81 tokens per session scan A db52cf1be826
veta CLAUDE.md is an instructions file published in the GitHub repository nerdconf/veta (0 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session, about $0.0004 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
pad CLAUDE.md
Instructions for PerpetualSoftware/pad, covering pad — development guide, what this is, architecture, build & install and quick iteration loop.
sverklo CLAUDE.md
Instructions for sverklo/sverklo, covering sverklo development, using sverklo tools, project structure and build & test.
brain-os AGENTS.md
Instructions for brainOS-HQ/brain-os, covering agents.md, context, the hard rule, tool routing (in order) and mutation safety.
brain-os copilot-instructions.md
Instructions for brainOS-HQ/brain-os, covering github copilot instructions, read this first, critical rules (also in agents.md) and known bugs (v0.4.1 fixes pending).
brain-os CLAUDE.md
Instructions for brainOS-HQ/brain-os, covering claude.md, agent instructions, build / dev, publish flow and project memory.
code-insights CLAUDE.md
Instructions for melagiri/code-insights, covering claude.md — code insights, project overview, development philosophy (critical), configuration hierarchy and documentation index.