Borrowing it
Nothing to install: this file belongs to Lanzelot1/claw-brain. 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/Lanzelot1/claw-brain/main/.claude/commands/new.mdgit clone --depth 1 https://github.com/Lanzelot1/claw-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/commands/lanzelot1/claw-brain/new)<a href="https://agentmods.dev/commands/lanzelot1/claw-brain/new"><img src="https://agentmods.dev/badge/commands/lanzelot1/claw-brain/new/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/commands/lanzelot1/claw-brain/new"><img src="https://agentmods.dev/badge/commands/lanzelot1/claw-brain/new.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.00007 | $0.00474 |
| Opus 5.5 | $0.00003 | $0.00190 |
| Sonnet 5.5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
new 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 2mo 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
The user wants to create a new area in the brain. An area is a knowledge domain (e.g. research, projects, notes, reading, health, recipes — anything).
Steps
- Ask: "What area do you want to create?" — Get a short name (lowercase, no spaces) and a one-line description.
- Ask: "What should be tracked in this area?" — Understand what kind of information goes here (e.g. reading list, project log, weekly notes, reference links).
- Create the knowledge file:
- Create
knowledge/{area}/folder - Write an initial
.mdfile (named after the primary concern, e.g.reading-list.md,log.md,notes.md) withsource:frontmatter and sections based on what they described - The
source:field should describe where the initial content came from (e.g."user input","onboarding") - Cross-reference: Search existing knowledge areas for related content. If found, suggest adding a
## Relatedsection in the new file with standard markdown links using[title](../other-area/file.md)format, and add reciprocal links in the related file(s)
- Create
- Update
memory/_index.md:- Add a new section header for the area
- Add a link to the main file with a 1-sentence description
- Add an entry under "Recently Added"
- Update
CLAUDE.md:- Add the new area to the Areas table (between the
<!-- Auto-updated by /new -->comment and the end of the table)
- Add the new area to the Areas table (between the
Git
After all file changes are done:
- Commit everything on a new branch (e.g.
add-{area}-area) - Push and open a PR titled "Add {area} area"
- Share the PR link with the user
Guidelines
- Keep area names lowercase, short, and descriptive
- The knowledge file should have useful section headers based on what the user described — not empty boilerplate
- If an area with that name already exists, tell the user and ask if they want to update it instead
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.
- 2mo ago First seen · 35 lines · 7 tokens per session scan A a9a70aa451e7
new is a command published in the GitHub repository Lanzelot1/claw-brain (11 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 474 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
screenshot
Screenshot a URL or document and read it visually.
obsidian-checkin
Ask the owner whether old people and project notes still hold - shows what each note says and when it was last checked, re-asks until answered, saves the news.
rem_help
Each section is printed verbatim by --help for the command it names. The agreed design is issue #1656; change a page there and here together.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
memory-forget
Command "memory-forget" from waittim/MemoryCustodian, covering memory-forget and review the preview, then apply its plan id.
memory-query
Query an existing graphify graph before rereading the full corpus, using query, path, or explain flows.