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/pyrodonkey/vexic/claude-mdgit clone --depth 1 https://github.com/PyroDonkey/vexicWrote 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/pyrodonkey/vexic/claude-md)<a href="https://agentmods.dev/instructions/pyrodonkey/vexic/claude-md"><img src="https://agentmods.dev/badge/instructions/pyrodonkey/vexic/claude-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.00021 | $0.00021 |
| Opus 5 | $0.00010 | $0.00010 |
| Sonnet 5 | $0.00004 | $0.00004 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
vexic 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 5d 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
Claude Code prompt context
Root pointer for Claude Code working in this repository.
@AGENTS.md
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.
- 5d ago First seen · 6 lines · 21 tokens per session scan A 64f864c20b23
vexic CLAUDE.md is an instructions file published in the GitHub repository PyroDonkey/vexic (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 21 tokens to every session, about $0.0001 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
claude-mem CLAUDE.md
Claude Code instructions for thedotmack/claude-mem, covering claude-mem: ai development instructions, build, file locations, requirements and documentation.
claude-mem copilot-instructions.md
Copilot instructions for thedotmack/claude-mem, a project described as: Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes…
codemem AGENTS.md
AGENTS.md instructions for kunickiaj/codemem, covering codemem, what runs where, commands worth using, gotchas agents usually miss and workflow rules specific to this repo.
engram CLAUDE.md
Claude Code instructions for techtheist/engram, covering engram — context for claude code, hard rules (locked — don't relitigate without reason), where things go, workflows & sharp edges and now / next (keywords).
claude-mem-sync CLAUDE.md
Claude Code instructions for lopadova/claude-mem-sync, covering claude.md — claude-mem-sync, what this project is, architecture, project structure and commands.
memofs AGENTS.md
AGENTS.md instructions for memo-fs/memofs, covering memofs — agent guidelines, monorepo architecture, core behavioral principles and workspace rules.