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/qa-vault/codelore/agents-mdgit clone --depth 1 https://github.com/qa-vault/codeloreWhat 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.01373 | $0.01373 |
| Opus 5 | $0.00687 | $0.00687 |
| Sonnet 5 | $0.00275 | $0.00275 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
codelore 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 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Context: codelore
This repository is a dual-ecosystem plugin — installable natively in both Claude Code and Codex CLI via the qa-vault/marketplace catalog. When working on this codebase, keep both ecosystems in sync.
Repository layout
codelore/
├── .claude-plugin/plugin.json # Claude Code manifest
├── .codex-plugin/plugin.json # Codex manifest
├── skills/
│ ├── exploratory-qa/SKILL.md
│ ├── document-feature/
│ │ ├── SKILL.md
│ │ └── references/doc_template.md
│ ├── consulting-project-docs/SKILL.md
│ └── migrate-project-docs/SKILL.md
├── README.md
├── LICENSE
└── AGENTS.md # this file
The skills/ directory is the single source of truth for skill content. Both manifests reference it — never duplicate skill files.
Skills overview
The plugin currently ships four skills, all auto-discovered from skills/. They are designed to compose into a feedback loop — written docs become indexed, the index gets auto-loaded into AI sessions, and a skeptical reviewer questions both the code and the docs.
document-feature— writes and maintains implementation docs with YAML frontmatter (name,description, optionaltriggers/related); regeneratesdocs/INDEX.mdafter every create or update. Excludes anything underdocs/plans/,plans/,specs/.migrate-project-docs— one-shot bulk migration that adds frontmatter to pre-existing docs and bootstrapsdocs/INDEX.md. Idempotent (re-runs do nothing on a fully migrated tree); skips plan folders; asks the user about ambiguous files before touching them.consulting-project-docs— router. Readsdocs/INDEX.mdand pulls only relevant docs into the agent's context whenever the user is planning, debugging, investigating, or onboarding. Silent no-op ifdocs/INDEX.mdis missing — never blocks, only nudges to runmigrate-project-docswhen appropriate.exploratory-qa— skeptical reviewer of code or implementation plans. Whendocs/INDEX.mdexists, loads relevant docs as additional material to question (not as authority); surfaces doc/code drift under the Domain Logic Fidelity lens; in plan mode, cross-checks plans against loaded docs.
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 · 101 lines · 1,373 tokens per session scan A 13edcef80431
codelore AGENTS.md is an instructions file published in the GitHub repository qa-vault/codelore (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,373 tokens to every session, about $0.0069 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.