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 skills/aidemd-mcp/server/brainnpx skills add aidemd-mcp/server --skill braingit clone --depth 1 https://github.com/aidemd-mcp/serverWhat 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.00145 | $0.00723 |
| Opus 5 | $0.00072 | $0.00362 |
| Sonnet 5 | $0.00029 | $0.00145 |
| Haiku 4.5 | $0.00015 | $0.00072 |
Grade A, and why
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brain — Signpost to the Brain
Pointer skill. The brain interface lives in the /aide:brain slash command —
this skill exists so any agent that needs brain access discovers it.
What the brain is
The brain is a knowledge store that lives external to the project and outside any single codebase. It can be a personal store for one developer or a shared store an entire team points at — when teammates wire their agents to the same brain, every member's agent reads and writes against the same playbook, research, project context, and conventions. That makes it the authoritative source for anything the team has agreed on or learned, and the place where new findings become reusable across projects and across people.
Typical contents: domain research, the coding playbook, project history and
context, journal logs, environment config, identity, references. AIDE's research
phase writes to it; the strategist and architect phases read from it; explorer
agents draw on it for context the code doesn't carry. The brain is a logical
surface — the underlying backend is an implementation detail the /aide:brain
command abstracts.
When to invoke /aide:brain
Trigger when the current task needs knowledge that isn't in the working directory:
- Unfamiliar domain. You're about to make a decision in a domain you have no loaded context for (e.g. cold email tactics, local SEO scoring, a vendor API quirk).
- Shared context referenced. The user says "check the brain," "what does the team do for X," "we already researched this," or names a project / research area / convention without giving you the file.
- Saving findings. You produced research, a decision, or a pattern the team will need again — synthesis the brain should own, not the repo.
What /aide:brain does
It discovers the brain's root navigation surface first — the brain owns its own structure and navigation rules — then follows those rules to find and return content (or write what it's been asked to save).
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.
- 2d ago First seen · 69 lines · 145 tokens per session scan A f972646bc478
brain is a skill published in the GitHub repository aidemd-mcp/server (3 stars, last pushed 3mo ago), licensed MIT. It adds 145 tokens to every session and 723 once invoked, about $0.0007 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 skills, from other repositories
chinese-documentation
中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。.
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
subagent-driven-development
当在当前会话中执行包含独立任务的实现计划时使用.