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 commands/evb87-tech/corpus/ingestgit clone --depth 1 https://github.com/evb87-tech/corpusWhat 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.00053 | $0.00521 |
| Opus 5 | $0.00026 | $0.00260 |
| Sonnet 5 | $0.00011 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
ingest 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 yesterday.
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
Pre-flight:
CORPUS_VAULT="${CORPUS_VAULT:-$CLAUDE_PLUGIN_OPTION_VAULT_PATH}"
if [ -z "$CORPUS_VAULT" ]; then
echo "No vault configured. Set CORPUS_VAULT (local dev) or configure the vaultPath userConfig option in the installed plugin (exposed as CLAUDE_PLUGIN_OPTION_VAULT_PATH). Neither is set. Run /init-vault <path> to scaffold a fresh vault, then export the path." >&2
exit 1
fi
Verify $CORPUS_VAULT/.corpus-vault exists. If not, refuse and tell the owner to run /init-vault <path>. See corpus-core/rules/08-vault-structure.md.
Run the ingestion protocol on: $ARGUMENTS
If $ARGUMENTS is empty, ingest every file in $CORPUS_VAULT/raw/ whose path does not appear in any wiki page's sources: frontmatter field. If $ARGUMENTS is a relative path, resolve it under $CORPUS_VAULT/raw/.
Delegate to the ingester subagent (see corpus-core/agents/ingester.md).
The full protocol is in corpus-core/rules/03-ingestion-protocol.md. Hard constraints:
- All paths below are relative to
$CORPUS_VAULT. - French content in wiki pages, English structural keywords. Sources may be EN or FR (translate at ingestion).
- One entity = one page. Update existing pages; do not duplicate.
- Cite every source in frontmatter
sources:AND inline. - Surface contradictions; do not resolve silently.
- Update
wiki/index.mdand append towiki/log.md. - Never modify
raw/. Never write intooutput/. - Anti-lissage: see
corpus-core/rules/07-anti-lissage.md.
When done, report: files ingested, pages created, pages modified, contradictions detected, broken [[links]], entities skipped.
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.
- yesterday First seen · 36 lines · 53 tokens per session scan A c507efa51ce0
ingest is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 521 once invoked, about $0.0003 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 commands, from other repositories
om-vault-upgrade
Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.
om-vault-audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-intake
Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.
om-wrap-up
Full session review before ending. Review context, ways of working, files modified, consistency, and suggest improvements.
om-peer-scan
Deep scan a peer's GitHub PRs for performance review preparation. Produces a structured analysis saved to perf/evidence/.