How do I install the Brain skill?

Run npx skillmds@latest add h-mmer/brain-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Brain skill do?

Manage the engagement brain. Subcommands: 'init' to set up, 'brief ' for pre-flight, 'status' for overview, 'exhausted [target]' to see dead ends. It is listed under Coding & Dev Tools on SkillMD.

Is Brain safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Brain?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Brain free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

h-mmer (@h-mmer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Brain by h-mmer — Agent Skill

Name: Brain
Author: h-mmer

File contents

Brain management: $ARGUMENTS

Route to the brain tool:

If "$ARGUMENTS" is "init": run uv run python3 ../../tools/brain.py init
If "$ARGUMENTS" starts with "brief": run uv run python3 ../../tools/brain.py brief <target>
If "$ARGUMENTS" is "status": run uv run python3 ../../tools/brain.py status
If "$ARGUMENTS" starts with "exhausted": run uv run python3 ../../tools/brain.py exhausted <target>
If "$ARGUMENTS" starts with "record": run uv run python3 ../../tools/brain.py record <target> <status> <technique> "<details>"

After running, also launch the brain agent to update the MEMORY.md index if any state changed.

Top-Tier Memory Bar

Bad memory makes the whole suite worse. Record facts as reusable evidence, not diary entries.

For every record, include:

target: canonical host or repo name
surface: endpoint, file, workflow, account role, or component
technique: vuln class plus variant, not just "tested auth"
status: confirmed, partial, exhausted, blocked, duplicate-risk, chain-pending
evidence: request id, file path, response marker, screenshot path, command output, or blocker
next_action: the exact command or test a future session should run

Never store "no bug" without the tested matrix. An exhausted entry must say what was tried and why that evidence is strong enough to skip it later.

Frequently asked questions

Brain