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.
/plugin marketplace add YaggoSEO/yaggo-brainnpx agentmods add plugins/yaggoseo/yaggo-brain/yaggo-braingit clone --depth 1 https://github.com/YaggoSEO/yaggo-brainWrote 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/yaggoseo/yaggo-brain/yaggo-brain)<a href="https://agentmods.dev/plugins/yaggoseo/yaggo-brain/yaggo-brain"><img src="https://agentmods.dev/badge/plugins/yaggoseo/yaggo-brain/yaggo-brain.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
yaggo-brain 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 5d 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": "yaggo-brain",
"version": "0.1.0",
"description": "yaggo-brain panel integration for Claude Code",
"mcp": {
"servers": {
"yaggo-brain": {
"command": "pnpm",
"args": ["--dir", "apps/mcp-server", "start"]
}
}
},
"hooks": {
"sessionStart": ".claude/hooks/yaggo-brain/session-start.js",
"sessionEnd": ".claude/hooks/yaggo-brain/session-end.js"
}
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 0 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.
- 5d ago First seen · 18 lines scan A e808396c1d0b
yaggo-brain is a plugin published in the GitHub repository YaggoSEO/yaggo-brain (2 stars, last pushed 2mo 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
agent-recall
Persistent memory for AI coding agents. SQLite knowledge graph with scoped entities, MCP tools, and LLM-summarized briefings.
code-refactoring
Code cleanup, refactoring automation, and technical debt management with context restoration.
agent-orchestration
Multi-agent system optimization, agent improvement workflows, and context management.
context-management
Context persistence, restoration, and long-running conversation management.
potpie
Project-memory context engine for Claude Code: surfaces preferences, prior bugs/fixes, infra topology, timeline context, and durable-capture prompts. Hooks are model-free; the in-session harness decides what is true and writes semantic graph mutations.
ctx
Fast local search and 'git blame' for agent sessions.