agentmods.dev

notebook

A command for keeping a timestamped lab notebook with entries, tags, commits, searches, and a chronological timeline.

In plain words
What is it for?
Use it to add notes, view recent entries, search by words or tags, and review the research timeline.
Why use it?
It keeps research notes and their connection to code changes in one searchable record.

Command for Claude Code

4 2d ago A scan 0 tokens original MIT
View the source file cdeust/ai-architect-mcp-codebase
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/cdeust/ai-architect-mcp-codebase/notebook
Clone the repo
git clone --depth 1 https://github.com/cdeust/ai-architect-mcp-codebase

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 403 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00403
Opus 5 $0.00000 $0.00201
Sonnet 5 $0.00000 $0.00081
Haiku 4.5 $0.00000 $0.00040

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

Security

Grade A, and why

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

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/research/notebook.md · 30 lines

What it actually says

Lab Notebook

Add entries to the lab notebook, view recent entries, or search by tag or keyword.

Instructions

  1. Parse $ARGUMENTS for the subcommand:

    • notebook add "<entry>" [--tag <tag>] [--commit <sha>] — add a timestamped entry
    • notebook show [--last <n>] — display entries (default: all; --last N for recent)
    • notebook search "<term>" — find entries matching a keyword or tag
    • notebook timeline — show chronological overview of all entries

  2. Add: Run tools/lab-notebook-manager.sh add "<entry>" with any provided flags. If a research session is active (check research/.session.json exists), include the current research question as context. Confirm the entry was added with its timestamp.

  3. Show: Run tools/lab-notebook-manager.sh show with optional --last <n>. Format the output for readability. If no notebook exists, suggest starting a research session first with /research-session start.

  4. Search: Run tools/lab-notebook-manager.sh search "<term>". Present matching entries clearly. If no matches, suggest alternative search terms or checking the timeline.

  5. Timeline: Run tools/lab-notebook-manager.sh timeline. Display the chronological list with entry count. Useful for getting an overview of research progression.

  6. If no subcommand given, run notebook show --last 5 as a sensible default.

  7. Entries should follow good lab notebook practice:

    • State what was done, not just what was found
    • Include the hypothesis being tested when relevant
    • Tag entries for later retrieval (e.g., --tag hypothesis, --tag result, --tag method)
    • Link commits when the entry corresponds to a code change

$ARGUMENTS

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 · 30 lines · 0 tokens per session scan A 96add7f7cc47

Subscribe to this mod's changes

notebook is a command published in the GitHub repository cdeust/ai-architect-mcp-codebase (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 403 tokens. 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-31.

Code reviewData and AIDatabasesbm25claude-codeclaude-code-pluginclean-architecturecode-graphcode-intelligence
Related

Other commands, from other repositories

brooks-audit

Run a Brooks-Lint architecture audit.

hyhmrright/brooks-lint · 7 tokens

brooks-health

Run a Brooks-Lint codebase health dashboard across all four dimensions.

hyhmrright/brooks-lint · 13 tokens

daily-standup

Génération Résumé Daily Stand-up.

TheBeardedBearSAS/claude-craft · 8 tokens

deploy

Build, test, deploy with staged rollout.

dinhnguyenngoc/spec-driven-claude-code · 10 tokens

fix-issue

Analyze and fix a reported bug or issue systematically.

dinhnguyenngoc/spec-driven-claude-code · 13 tokens

simplify

Reduce complexity without changing behavior — code simplification.

dinhnguyenngoc/spec-driven-claude-code · 12 tokens