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/cyberlife-coder/velesdb/agents-mdgit clone --depth 1 https://github.com/cyberlife-coder/VelesDBWhat 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.04804 | $0.04804 |
| Opus 5 | $0.02402 | $0.02402 |
| Sonnet 5 | $0.00961 | $0.00961 |
| Haiku 4.5 | $0.00480 | $0.00480 |
Grade A, and why
VelesDB 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 211 lines · 4,804 tokens per session scan A c082389187db
VelesDB AGENTS.md is an instructions file published in the GitHub repository cyberlife-coder/VelesDB (90 stars, last pushed 3d ago), with no licence file. It adds 4,804 tokens to every session, about $0.0240 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
gno AGENTS.md
Instructions for gmickel/gno, covering knowledge cutoff warning, apis - bun first!, must use bun, acceptable node:\ (no bun equivalent) and testing.
loomem CLAUDE.md
Instructions for vvooki-sys/loomem, covering claude.md — rules for ai code generators in the loomem repo, router — read the subset that applies, five hard rules (never break these), build & run and repo map (where things live).
vecgrep CLAUDE.md
Instructions for jeffbai996/vecgrep, covering vecgrep — claude code working notes, what this is, architecture cheat sheet, design rules and don'ts.
palace-rs AGENTS.md
Instructions for AncientiCe/palace-rs, covering agent rules, 1. test-driven development (tdd), 2. quality gates on every task, 3. no plan markdown files and 4. internal api discipline.
loomem AGENTS.md
Instructions for vvooki-sys/loomem: The contributor rules for AI coding agents in this repository live in CLAUDE.md — that file is the single source of truth.
cortexmem CLAUDE.md
Claude Code instructions for gonzalonicolasr/cortexmem, covering memoria - persistent memory system, memory protocol, when to save (automatic - do this without being asked), structured format and session lifecycle.