Borrowing it
Nothing to install: this file belongs to aidemd-mcp/server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aidemd-mcp/server/main/.claude/skills/aide-brain-author/SKILL.mdgit clone --depth 1 https://github.com/aidemd-mcp/serverWrote 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/skills/aidemd-mcp/server/aide-brain-author)<a href="https://agentmods.dev/skills/aidemd-mcp/server/aide-brain-author"><img src="https://agentmods.dev/badge/skills/aidemd-mcp/server/aide-brain-author/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/skills/aidemd-mcp/server/aide-brain-author"><img src="https://agentmods.dev/badge/skills/aidemd-mcp/server/aide-brain-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00190 | $0.02299 |
| Opus 5.5 | $0.00076 | $0.00920 |
| Sonnet 5.5 | $0.00038 | $0.00460 |
| Haiku 4.5 | $0.00019 | $0.00230 |
Grade A, and why
aide-brain-author 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aide-brain-author — Write a Brain Config for Any Backend
The brain config tells every AIDE agent how to reach the project's brain: the launcher that starts the brain's MCP server, and a fixed set of contract sections, each with a published purpose. The bundled template fills them for its own default backend. This skill writes them for the user's backend instead.
Every section list, role, purpose and template text comes from aide_brain. Never write a section list or a purpose from memory, and never copy one from another config.
Hard constraints
- Structure is checked; content is the user's. The draft check confirms every required field and section is present and well-formed. Whether the prose works for the backend is the user's call. Confirm each section with the user before moving on.
- One section at a time. Read one section, write it with the user, confirm, then read the next. Never fetch the whole template up front.
- Draft first when writing a whole config. Write the new config to
.aide/config/brain.aide.draft. The live config at.aide/config/brain.aidechanges only at the swap step, and only on the user's yes. The one exception is adding missing sections (below), which edits the live config in place because the user already chose to repair it. - Never invent backend tool names. Ask the user how their backend's MCP server is launched and which tools it exposes, or read its documentation with them. If they don't know yet, leave a clearly marked TODO in that section and tell them.
The tool calls
aide_brain is read-only in every mode below. None of them reads or depends on the project's current brain config.
aide_brain({ source: "contract" })returns{ sections }: every contract section in order, each with itsmarker,role(liveorseed) andpurpose, and no text.aide_brain({ source: "template", kind: "launcher" })returns{ template, purpose }: the bundled template's frontmatter lines (between the two---fences) and what the launcher must do.aide_brain({ source: "template", kind: <marker> })returns{ template, purpose }: the bundled template's text for that one section and what the section must do.aide_brain({ source: "draft", path: ".aide/config/brain.aide.draft" })returns{ outcome, instructions }.outcomeisvalid,invalid(with afault:missing-sectionsnaming the sections, ormalformedwith areason),absent, orrefused(the path is outside the project). It uses the same rules and fault wording as the live config check, so avaliddraft is structurally ready to swap in.
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 Changed · -4 lines 73d2bad2dbe4
- 19d ago First seen · 126 lines · 190 tokens per session scan A e5310eb77816
aide-brain-author is a skill published in the GitHub repository aidemd-mcp/server (4 stars, last pushed 2d ago), licensed MIT. It adds 190 tokens to every session and 2,299 once invoked, about $0.0008 per session on Opus 5.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-10-12.
Other skills, from other repositories
papi-plan
Invoke when starting a new PAPI cycle. Covers plan generation, board management, and cycle scoping rules.
papi-idea
Invoke when submitting backlog ideas, registering docs, or filing research. Covers idea pipeline and doc registry conventions.
papi-integration-recipe
Use when the user wants to feed data from a connected MCP tool (Sentry, Linear, GitHub, Slack, or any other) into PAPI. Demonstrates the "host agent = integration bus" pattern: read from the external tool, map to PAPI shape, write via PAPI tool. PAPI never owns connectors — the user's AI session passes data between…
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.
papi-strategy
Invoke when running strategyreview or making Active Decision changes. Covers strategy review cadence and AD lifecycle.