agentmods.dev

corpus: Instructions file for Codex

AGENTS.md

corpus AGENTS.md is an instructions file for Codex, OpenCode from evb87-tech/corpus. It costs 901 tokens per session, scanned A, original, MIT.

Repository instructions for coding agents working on the Corpus project, which stores knowledge in an Obsidian vault. They explain the project layout, file rules, and where the vault is located.

In plain words
What is it for?
Use them when changing Corpus code, agents, commands, or scaffolding, especially when working with the separate vault and its raw, wiki, and output folders.
Why use it?
They give different coding tools the same rules, reducing accidental edits to user content or the wrong repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions CLAUDE.md; mentions subagents.

This is evb87-tech/corpus's own configuration. It tells Codex and OpenCode how to work on corpus itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything corpus configures →

not rated 1repo 5mo ago A scan 901 tokens original MIT
View source ↗ evb87-tech/corpus
Reuse

Borrowing it

Nothing to install: this file belongs to evb87-tech/corpus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/evb87-tech/corpus/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/evb87-tech/corpus

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for corpus AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/evb87-tech/corpus/agents-md/github.svg)](https://agentmods.dev/instructions/evb87-tech/corpus/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/evb87-tech/corpus/agents-md"><img src="https://agentmods.dev/badge/instructions/evb87-tech/corpus/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for corpus AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/evb87-tech/corpus/agents-md"><img src="https://agentmods.dev/badge/instructions/evb87-tech/corpus/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 901 This file is loaded in full into every session.
When invoked 901 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00901 $0.00901
Opus 5.5 $0.00360 $0.00360
Sonnet 5.5 $0.00180 $0.00180
Haiku 4.5 $0.00090 $0.00090

Measured 1mo ago against content hash 32e94ffba421, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

corpus 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 1mo 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.

AGENTS.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Agent-agnostic instructions. For Claude-specific guidance, see CLAUDE.md. The rules below are equivalent — only the loading convention differs (this file is read by Codex, Gemini CLI, Aider, OpenCode, etc.).

Two repos, one system

  • This repo (corpus) is the engine: code, agents, rules, slash commands, scaffolding. Public. No user content.
  • The vault is a separate Obsidian directory the user owns and tracks in their own (typically private) git repo. Contains raw/, wiki/, output/, .obsidian/. The engine operates on it via the CORPUS_VAULT env var.
$CORPUS_VAULT/
├── raw/            sources (read-only for agents)
├── wiki/           compiled pages (agent-only writes, French content)
├── output/         deliverables (briefs, notes, syntheses)
└── .obsidian/      Obsidian config

A user runs /init-vault <path> once to scaffold a fresh vault, sets export CORPUS_VAULT=<path>, then uses the slash commands. Their vault never enters this repo.

Hard rules

  1. Never modify $CORPUS_VAULT/raw/. The owner curates what enters.
  2. Only agents write to $CORPUS_VAULT/wiki/. The owner does not hand-edit.
  3. output/ never feeds back into wiki/.
  4. Wiki content is in French; sources may be EN or FR (translate at ingestion). Structural keywords (frontmatter fields, filenames, fixed H2 names) stay in English.
  5. One entity, one page in wiki/. Update; do not duplicate.
  6. Cite every claim back to a file in raw/.
  7. Surface contradictions; never harmonize silently.
  8. Never invent a source. Never complete with training-data knowledge unless the owner explicitly asks.
  9. Never produce type: synthesis as a wiki page. Synthesis goes to output/ only.
  10. Never assume the vault path. Resolve via $CORPUS_VAULT. Refuse to operate if unset.

Repo layout — monorepo of two plugins

  • corpus-core/ — the engine plugin (rules, agents, commands, plugin manifest)
  • corpus-pm/ — first use-case pack, depends on corpus-core
  • .claude-plugin/marketplace.json publishes both
  • Repo-wide docs at docs/, CLAUDE.md, AGENTS.md, CONTRIBUTING.md

Read the full file on GitHub · 62 lines

Changes

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.

  1. 1mo ago First seen · 62 lines · 901 tokens per session scan A 32e94ffba421

Subscribe to this mod's changes

corpus AGENTS.md is an instructions file published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 5mo ago), licensed MIT. It adds 901 tokens to every session, about $0.0036 per session on Opus 5.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.

Claude CodeLLMclaude-code-marketplaceclaude-code-pluginknowledge-managementobsidian
Related

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).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens