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.
git clone --depth 1 https://github.com/evb87-tech/corpusWrote 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/plugins/evb87-tech/corpus/corpus-core)<a href="https://agentmods.dev/plugins/evb87-tech/corpus/corpus-core"><img src="https://agentmods.dev/badge/plugins/evb87-tech/corpus/corpus-core/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.
<a href="https://agentmods.dev/plugins/evb87-tech/corpus/corpus-core"><img src="https://agentmods.dev/badge/plugins/evb87-tech/corpus/corpus-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
corpus-core 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.
What it actually says
{
"name": "corpus-core",
"version": "0.1.0",
"description": "Engine for an LLM-curated second brain. Karpathy LLM-wiki pattern with anti-lissage spec, FR-by-default content, three query postures.",
"author": {
"name": "evb87-tech",
"url": "https://github.com/evb87-tech"
},
"homepage": "https://github.com/evb87-tech/corpus",
"repository": "https://github.com/evb87-tech/corpus",
"license": "MIT",
"keywords": ["second-brain", "wiki", "knowledge-management", "obsidian", "karpathy", "anti-lissage"],
"dependencies": [],
"userConfig": {
"vaultPath": {
"type": "directory",
"title": "Corpus vault path",
"description": "Absolute path to your corpus vault directory (raw/, wiki/, output/). Run /init-vault to scaffold one if needed.",
"sensitive": false
}
}
}
What it installs
The manifest is a name and a version. 23 commands, 3 agents travel with it, and installing the plugin installs all of them — 333 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command check-03-trap-silent-fix A 0 tokens
- Command draft-02-edge-absent-wiki A 0 tokens
- Command draft-03-trap-wiki-feedback A 0 tokens
- Command ingest-02-edge-contradiction A 0 tokens
- Command ingest-03-trap-padding A 0 tokens
- Command query A 0 tokens
- Command query-contradictor-01-happy A 0 tokens
- Command query-contradictor-02-edge-asymmetric A 0 tokens
- Command query-contradictor-03-trap-no-contradictions A 0 tokens
- Command query-research-01-happy A 0 tokens
- Command query-research-02-edge-partial A 0 tokens
- Command query-research-03-trap-no-coverage A 0 tokens
- Command query-synthesis-01-happy A 0 tokens
- Command query-synthesis-02-edge-mixed-signals A 0 tokens
- Command query-synthesis-03-trap-wiki-destination A 0 tokens
- Command check-01-happy A 0 tokens
- Command check-02-edge-stale-links A 0 tokens
- Command draft-01-happy A 0 tokens
- Command ingest A 53 tokens
- Command ingest-01-happy A 0 tokens
- Command check A 43 tokens
- Command draft A 38 tokens
- Command init-vault C 32 tokens
- Agent contradictor A 61 tokens
- Agent ingester A 54 tokens
- Agent librarian A 52 tokens
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.
- 1mo ago First seen · 23 lines scan A 262f2cd949c5
corpus-core is a plugin published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
superbrain
Automatic Claude Code -> Obsidian second brain: zero-config session capture, hybrid search, autonomous recall, daily/lessons/preferences.
memex
Collaborative memory for human-AI work — persistent, searchable, interconnected.
kb
Build and maintain LLM-powered knowledge bases as Obsidian wikis with compile, query, lint, and evolve workflows.
obsidian-chronicle
Auto-records Claude Code sessions as structured Obsidian notes + Daily Note entries (via the SessionEnd/PreCompact hooks and /done), and ships the obsidian-vault agent — the unified handler for all Obsidian vault work (create, edit, search, organize notes, tasks, canvases, bases). Configure with…
llm-wiki
Build a shared Markdown knowledge base with local hybrid search and an optional evidence-linked workflow to capture task lessons, evaluate skill improvements, and apply or roll back tested changes.
vault-pkm
Bidirectional knowledge flow between Claude Code and Obsidian — 20 MCP tools, skills, and hooks for PKM.