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.
npx agentmods add commands/maxwellsdm1867/wheeler/notegit clone --depth 1 https://github.com/maxwellsdm1867/wheelerWhat 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 | $0.00021 | $0.00964 |
| Opus 5 | $0.00010 | $0.00482 |
| Sonnet 5 | $0.00004 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00096 |
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. 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:
- "What's the thought?" (required — this becomes the note content)
- "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
-
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.
-
Call
add_notewith:content: the full note texttitle: the extracted short titlecontext: what prompted it (empty string if not provided)
This creates the graph node in
knowledge/and returns the node ID. -
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 (usemkdir -p .notes). -
Call
index_nodewith the new node ID, label"ResearchNote", and the content text to make it searchable.
Link it (mandatory if a plan is active, otherwise optional)
- 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.
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 First seen · 94 lines · 21 tokens per session scan C 26c10d6aaf2d
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.
Other commands, from other repositories
export
Export a knowledge abstract to an Obsidian vault — a folder of Markdown notes linked by [[wikilinks]].
bootstrap-memory
RUN { git ls-files; git ls-files --others --exclude-standard; } 2>/dev/null | sort -u | xargs wc -l 2>/dev/null | sort -rn | head -150 READ README.md.
maestro-issue
Intent-driven issue lifecycle management — describe what you want in natural language (报告一个 bug / 列出开放 issue / 关掉 ISS-xxx / 关联到 task / 扫描发现问题) and the workflow routes to the right operation. Operates on .workflow/issues/. 知识管理走 /maestro-knowledge;knowhow 沉淀走 /maestro-knowhow;约束规则走 /maestro-spec。Triggers on "issue 管理"…
twining:export
Export Twining state as markdown for context handoff or archival.
formula-f10
../../../core/thinkingos/agents/observer.md.
formula-f8
../../../core/thinkingos/agents/securityauditor.md.