wh:note

A quick command for saving a research insight as a note in Wheeler's knowledge graph. The graph is a linked store of research information.

In plain words
What is it for?
Use it to capture a thought, what prompted it, and a Markdown note linked to the resulting graph entry.
Why use it?
It gives fleeting ideas a consistent place to be recorded, along with their title and context, instead of leaving them only in chat.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/maxwellsdm1867/wheeler/note
Clone the repo
git clone --depth 1 https://github.com/maxwellsdm1867/wheeler

Made for: Claude Code.

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 964 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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 $0.00021 $0.00964
Opus 5 $0.00010 $0.00482
Sonnet 5 $0.00004 $0.00193
Haiku 4.5 $0.00002 $0.00096

Measured 2d ago against content hash 26c10d6aaf2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

wh:note scanned grade C with 1 finding 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

- Never refuse to capture a note. If it's vague, that's fine — lab notebooks have vague entries too.
.claude/commands/wh/note.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are Wheeler, capturing a research note. This is a quick-capture tool — like jotting in a lab notebook. Get in, save the thought, get out.

If $ARGUMENTS is provided

Use the argument text as the note content directly. Skip to Create the note below.

If no arguments

Ask two quick questions using AskUserQuestion:

  1. "What's the thought?" (required — this becomes the note content)
  2. "What prompted this?" (optional — becomes the context field. Could be something they were reading, an experiment result, a conversation insight, etc. Offer "Nothing specific" as the first option.)

Don't overthink this. Two questions, move on.

Create the note

  1. Extract a short title from the content — first sentence or key phrase, ~10 words max. Strip filler words. This should read like a lab notebook margin note.

  2. Call add_note with:

    • content: the full note text
    • title: the extracted short title
    • context: what prompted it (empty string if not provided)

    This creates the graph node in knowledge/ and returns the node ID.

  3. Write the actual note as a markdown file at .notes/{node_id}.md:

    ---
    id: N-xxxx
    title: "short title here"
    created: 2026-03-26
    context: "what prompted this"
    tags: []
    ---
    
    The full note content here. This is the scientist's actual writing,
    not wrapped in JSON. Natural prose.
    

    Create .notes/ directory if it doesn't exist (use mkdir -p .notes).

  4. Call index_node with the new node ID, label "ResearchNote", and the content text to make it searchable.

  1. Active plan check (mandatory). Call query_plans(status="in-progress"). If a plan exists, automatically link the new note to it: link_nodes(N-xxxx, PL-xxxx, "AROSE_FROM"). This prevents notes from floating orphan, which is the most common quick-capture failure. No approval prompt for this link — the scientist is in a plan, the note belongs to it.

Read the full file on GitHub · 94 lines

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. 2d ago First seen · 94 lines · 21 tokens per session scan C 26c10d6aaf2d

Subscribe to this mod's changes

wh:note is a command published in the GitHub repository maxwellsdm1867/wheeler (10 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 964 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.