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/checkgit 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.00043 | $0.00438 |
| Opus 5 | $0.00022 | $0.00219 |
| Sonnet 5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
check 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 maintenance protocol on $CORPUS_VAULT/wiki/. Delegate to the librarian subagent (see corpus-core/agents/librarian.md).
Full protocol: corpus-core/rules/06-maintenance-check.md. Cover both scopes:
Structural (mechanical):
- broken
[[wikilinks]] - orphan pages (no incoming links)
- ultra-connected pages (> 20 incoming links)
- stale (
last_updated> 6 months and no new source since) wiki/index.mdout of sync- frontmatter / section / filename violations
Content-level (Karpathy's full lint scope):
- important concepts lacking pages
- stale claims superseded by newer raw sources
- data gaps (high incoming-link count, thin body)
- suggested investigations (3–5 open questions the wiki can't answer well)
Append a one-line summary to wiki/log.md. Read-only otherwise — do NOT auto-fix. Report findings; the owner decides.
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 · 43 tokens per session scan A 6dd5d27cedd9
check is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 438 once invoked, about $0.0002 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-self-review
Write your self-assessment for your company's review tool. Produces project impact descriptions, competency self-assessments (current level / next level), principles, and growth plan — all within character limits, fact-checked, strategically calibrated.
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.