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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/pyrodonkey/vexic/agents-md"><img src="https://agentmods.dev/badge/instructions/pyrodonkey/vexic/agents-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.05319 | $0.05319 |
| Opus 5 | $0.02660 | $0.02660 |
| Sonnet 5 | $0.01064 | $0.01064 |
| Haiku 4.5 | $0.00532 | $0.00532 |
Grade A, and why
vexic 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.
How it starts
The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vexic Agent Instructions
Contributor and maintainer guidance for automated agents working in this repository. This is engineering workflow documentation, not the product README.
Single source of truth for agents working in this repository. Plain markdown, no tool-specific syntax.
Project
Vexic is the standalone memory system extracted from a private source host: a provenance-first, replayable memory core for long-running agents.
The current v0.1 package is a local Python core with:
- public contract models in
src/vexic/contract - a local SQLite-backed reference service in
src/vexic/service.py - memory storage, retrieval, and Light/REM/Deep primitives under
src/vexic - conformance and reliability tests under
tests
Managed hosted auth stacks, billing, dashboards, public marketplace MCP, mature
remote MCP, and managed operations are out of scope for v0.1. The read-only
local stdio MCP MVP is the local adapter slice. The in-process hosted MVP shell
in src/vexic/hosted.py may bind Vexic-scoped API keys to
tenant/project/capability scope for internal staging, and the hosted FastAPI
adapter may expose the narrow read-only native HTTP MCP /mcp slice described
in ADR 0010. This is not a public HTTP service or production control plane. The
private source host remains the first-party consumer; see docs/provenance.md
for extraction provenance.
Architecture Boundaries
These are settled boundaries. Do not reintroduce private host runtime code into Vexic.
Package Boundary
- Vexic code lives under
src/vexic. - Repo-local host adapter files under
adapters/may import publicvexic.*APIs as consumers. They are not Vexic package runtime, and provider-secret or live-model wiring belongs there rather than insrc/vexic. - Runtime code must not import legacy
engine.*modules. - Private source-host paths may appear in provenance or compatibility docs, not as operational dependencies.
LocalMemoryServiceis a reference local adapter, not a hosted service.- Host-owned extension tables in an existing SQLite database must be preserved.
Vexic schema initialization must not create or take ownership of private-host
extension tables such as
background_tool_audit.
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 · 482 lines · 5,319 tokens per session scan A 8dfb886c7630
vexic AGENTS.md is an instructions file published in the GitHub repository PyroDonkey/vexic (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 5,319 tokens to every session, about $0.0266 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
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
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
Instructions for memo-fs/memofs, covering memofs — agent guidelines, monorepo architecture, core behavioral principles and workspace rules.