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 skills add davistroy/claude-marketplace --skill lab-notebookgit clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/skills/davistroy/claude-marketplace/lab-notebook)<a href="https://agentmods.dev/skills/davistroy/claude-marketplace/lab-notebook"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/lab-notebook/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/skills/davistroy/claude-marketplace/lab-notebook"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/lab-notebook.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.00104 | $0.05023 |
| Opus 5.5 | $0.00042 | $0.02009 |
| Sonnet 5.5 | $0.00021 | $0.01005 |
| Haiku 4.5 | $0.00010 | $0.00502 |
Grade A, and why
lab-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lab Notebook
Establish mandatory, structured experiment logging for a project. Once initialized, every system modification, benchmark, configuration change, build attempt, and debugging step MUST be logged in LAB_NOTEBOOK.md — no exceptions.
The notebook combines three proven documentation patterns:
- Scientific lab notebook — hypothesis-driven entries with environment context and reproducibility
- Architecture Decision Records — decisions with alternatives considered and lifecycle tracking
- Incident postmortem — blameless failure analysis, action items, and "what went well"
Input
Arguments: $ARGUMENTS
Supported arguments:
init— Full initialization: discover prior work, create LAB_NOTEBOOK.md, inject CLAUDE.md rulesentry "title"— Add a new numbered entry to an existing notebookstatus— Show notebook health: entries, staleness, open action items, active decisionsrotate— Archive the oldest experiment entries todocs/archive/once the log grows large, keeping the living sections and recent entries. Preserves every decision (a move, never a delete).- No arguments — Same as
initif no notebook exists, same asstatusif one does
Phase 0: Self-Invocation Confirmation
This skill can be model-invoked, and every mode except status writes to the project —
init creates LAB_NOTEBOOK.md and injects binding rules into CLAUDE.md; entry
appends; rotate moves entries into docs/archive/. None of that may happen unasked.
If you are invoking this skill on your own initiative — because the work looks
experimental, a benchmark is starting, or the user said something like "I keep losing track
of what I tried" — rather than the user typing /lab-notebook, confirm first with
AskUserQuestion:
{
"questions": [
{
"question": "Set up a lab notebook for this project?",
"header": "Notebook",
"multiSelect": false,
"options": [
{
"label": "Yes, initialize it",
"description": "Creates LAB_NOTEBOOK.md and adds logging rules to CLAUDE.md that make an entry a precondition for every system-modifying action"
},
{
"label": "No, not now",
"description": "Nothing is written; you can run /lab-notebook yourself at any time"
}
]
}
]
}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 339 lines · 104 tokens per session scan A 915ca039230c
lab-notebook is a skill published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 18d ago), licensed MIT. It adds 104 tokens to every session and 5,023 once invoked, about $0.0004 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-09-04.
Other skills, from other repositories
trace
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode.
pos-tagging-fixes
Diagnose and fix part-of-speech tagging in the compromise source repository. Choose between lexical data, ambiguity clues, indexed neighbour rules, preTagger logic, and postTagger patterns with attention to execution order, side effects, runtime, and bundle size. Use for internal tagging changes, not ordinary…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
linear-solvers
Select and configure linear solvers for systems Ax=b in dense and sparse problems. Use when choosing direct vs iterative methods, diagnosing convergence issues, estimating conditioning, selecting preconditioners, or debugging stagnation in GMRES/CG/BiCGSTAB.
nonlinear-solvers
Select and configure nonlinear solvers for f(x)=0 or min F(x). Use for Newton methods, quasi-Newton (BFGS, L-BFGS), Broyden, Anderson acceleration, diagnosing convergence issues, choosing line search vs trust region, and analyzing Jacobian quality.
numerical-stability
Analyze and enforce numerical stability for time-dependent PDE simulations. Use when selecting time steps, choosing explicit/implicit schemes, diagnosing numerical blow-up, checking CFL/Fourier criteria, von Neumann analysis, matrix conditioning, or detecting stiffness in advection/diffusion/reaction problems.