claw-brain: Command for Claude Code

.claude/commands/new.md

new is a command for Claude Code from Lanzelot1/claw-brain. It costs 7 tokens per session (474 once invoked), scanned A, original, MIT.

A command for adding a new knowledge area to a personal collection of notes and reference files. It asks what the area should contain, creates a Markdown file, and connects it to related areas.

In plain words
What is it for?
Use it to start areas such as research, projects, reading, health, or recipes, with an index entry and links to related files.
Why use it?
It gives new information a consistent place and keeps the collection easier to navigate. It also helps prevent related notes from becoming isolated.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is Lanzelot1/claw-brain's own configuration. It tells Claude Code how to work on claw-brain itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claw-brain configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Lanzelot1/claw-brain/main/.claude/commands/new.md
Clone the repo
git clone --depth 1 https://github.com/Lanzelot1/claw-brain

Made for: Claude Code.

Wrote 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.

agentmods badge for new

README.md
[![agentmods](https://agentmods.dev/badge/commands/lanzelot1/claw-brain/new/github.svg)](https://agentmods.dev/commands/lanzelot1/claw-brain/new)
Your own site
<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.

agentmods 80×15 button for new

Your own site · 80×15
<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>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 474 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2mo ago against content hash a9a70aa451e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/commands/new.md · 35 lines

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

  1. Ask: "What area do you want to create?" — Get a short name (lowercase, no spaces) and a one-line description.
  2. 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).
  3. Create the knowledge file:
    • Create knowledge/{area}/ folder
    • Write an initial .md file (named after the primary concern, e.g. reading-list.md, log.md, notes.md) with source: 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 ## Related section in the new file with standard markdown links using [title](../other-area/file.md) format, and add reciprocal links in the related file(s)
  4. 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"
  5. Update CLAUDE.md:
    • Add the new area to the Areas table (between the <!-- Auto-updated by /new --> comment and the end of the table)

Git

After all file changes are done:

  1. Commit everything on a new branch (e.g. add-{area}-area)
  2. Push and open a PR titled "Add {area} area"
  3. 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
Changes

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.

  1. 2mo ago First seen · 35 lines · 7 tokens per session scan A a9a70aa451e7

Subscribe to this mod's changes

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.