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 skills/eins78/agent-skills/lab-notesnpx skills add eins78/agent-skills --skill lab-notesgit clone --depth 1 https://github.com/eins78/agent-skillsWrote 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/eins78/agent-skills/lab-notes)<a href="https://agentmods.dev/skills/eins78/agent-skills/lab-notes"><img src="https://agentmods.dev/badge/skills/eins78/agent-skills/lab-notes.svg" alt="Measured on agentmods" 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 | $0.00074 | $0.02236 |
| Opus 5 | $0.00037 | $0.01118 |
| Sonnet 5 | $0.00015 | $0.00447 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
lab-notes 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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lab Notes
Structured experiment management with append-only running logs, optional hypotheses, and formal verdicts. Two modes: Rigorous (full scientific method) and Freeform (exploratory, structure grows organically). Works for any hypothesis-first exploration — technical experiments, feature planning, product ideas, infrastructure changes.
Workflow: FRAME -> SETUP -> RUN -> ANALYZE -> VERDICT
FRAME -> SETUP -> RUN -> ANALYZE -> VERDICT
| | |
| (freeform: skip to) | (freeform: skip to) |
+--------------------+ |
v
GRADUATE / ARCHIVE / ITERATE / PIVOT
Mode Selection
Ask at experiment start: "Is this a structured experiment or are you just trying something out?"
| Answer | Mode | Behavior |
|---|---|---|
| "Structured" / "rigorous" / "I have a hypothesis" | Rigorous | All REQUIRED sections enforced via phase gates |
| "Just trying" / "exploring" / vague / casual | Freeform | Title + motivation required; everything else optional, asked but skippable |
Set mode: rigorous or mode: freeform in LOG frontmatter. Mode can be upgraded (freeform -> rigorous) at any time.
In Freeform mode, still ASK for hypothesis, success criteria, and fail condition — but accept "skip", casual one-liners, or "I'll figure that out later." A casual hypothesis is fine: "I bet we can do X with Y and it'd be really cool."
Dispatcher: /lab-notes
Analyzes current state and suggests next action:
- Scan
experiments/*/LOG-*.mdfor YAML frontmatter - Check timebox deadlines against today (if set)
- Detect if user is in an experiment directory
- Report status table:
## Active Experiments
| Experiment | Phase | Mode | Started | Timebox | Status |
|------------|-------|------|---------|---------|--------|
| local-llm | RUN | freeform | 2026-03-11 | open-ended | 3 log entries |
| ev-charging | FRAME | rigorous | 2026-03-12 | 2026-04-01 | OVERDUE |
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.
- 4d ago First seen · 198 lines · 74 tokens per session scan A 6727bf69c520
lab-notes is a skill published in the GitHub repository eins78/agent-skills (2 stars, last pushed 17d ago), licensed MIT. It adds 74 tokens to every session and 2,236 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
iso-24495-3
Sector-specific Plain Language standard for science and technical writing (ISO 24495-3:2026). Applied during software documentation, architecture specs, and technical analysis.
using-cesiumjs-skills
Use when starting any conversation involving CesiumJS development - provides orientation on available domain skills and how they activate.
shipping-reproducible-results
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
discovery-toolbox
A routed repertoire of 90 scientific thinking operators for biological research agents - visual reasoning, detectability and information budgets, search reframing, causal identification, competing explanations, observation and selection processes, pipeline artifact diagnosis, effort allocation, and confirmation…
running-decision-grade-data-science
Orchestrate an end-to-end data analysis or machine learning project from decision framing through reproducible handoff. Use when a request spans multiple lifecycle stages or an ambiguous modeling request must become a decision-ready result; use narrower audit or experiment-design skills for isolated reviews.
designing-leakage-safe-experiments
Design leakage-safe machine learning experiments that mirror real deployment and support fair model comparisons. Use when defining prediction timing, feature eligibility, train-validation-test splits, baselines, metrics, or controlled model iterations; not for auditing whether raw labels are trustworthy.