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/yarlson/yarstackWrote 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/yarlson/yarstack/yarbrain)<a href="https://agentmods.dev/plugins/yarlson/yarstack/yarbrain"><img src="https://agentmods.dev/badge/plugins/yarlson/yarstack/yarbrain/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/yarlson/yarstack/yarbrain"><img src="https://agentmods.dev/badge/plugins/yarlson/yarstack/yarbrain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yarbrain 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- yarstack — 95% identical, 11 lines differ
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "yarbrain",
"displayName": "Yarbrain",
"version": "0.2.0",
"description": "A reviewable Markdown second brain for Codex and Claude Code.",
"author": {
"name": "Yar Kravtsov",
"url": "https://github.com/yarlson"
},
"homepage": "https://github.com/yarlson/yarstack",
"repository": "https://github.com/yarlson/yarstack",
"license": "MIT",
"keywords": [
"codex",
"claude-code",
"memory",
"knowledge-management"
]
}
What it installs
The manifest is a name and a version. 6 skills, 3 hooks travel with it, and installing the plugin installs all of them — 317 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 21 lines scan A 06c8d475d460
yarbrain is a plugin published in the GitHub repository yarlson/yarstack (3 stars, last pushed 2d 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
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
esp32-cpp
Evidence-first ESP32 firmware guidance for hardware, FreeRTOS, memory, peripherals, and field failures.
owndiff
Local ownership gate and multiple choice question approval skill for AI-assisted code diffs.
deja
deja-vu memory for Gemini CLI: the coding sessions already on your disk — Gemini CLI, Claude Code, Codex, Cursor and thirty-eight more — searchable and recalled, including work from before it was installed.
project-brain
Folder structure + collaboration protocol so AI sessions can resume project context after compaction or window switch. One brain/ folder, 5 core files (PROJECT/MAP/STATUS/DECISIONS/HANDOFF), and a topic taxonomy.
memex
Zettelkasten-based agent memory system with bidirectional links.