Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add slamb2k/mad-skills/plugin install mad-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/slamb2k/mad-skills/logbook)<a href="https://agentmods.dev/skills/slamb2k/mad-skills/logbook"><img src="https://agentmods.dev/badge/skills/slamb2k/mad-skills/logbook/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/slamb2k/mad-skills/logbook"><img src="https://agentmods.dev/badge/skills/slamb2k/mad-skills/logbook.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.00153 | $0.03684 |
| Opus 5 | $0.00077 | $0.01842 |
| Sonnet 5 | $0.00031 | $0.00737 |
| Haiku 4.5 | $0.00015 | $0.00368 |
Grade A, and why
logbook 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 3d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logbook - What's On Deck
When this skill is invoked, IMMEDIATELY output the banner below before doing anything else.
Pick ONE tagline at random — vary your choice each time.
CRITICAL: Reproduce the banner EXACTLY character-for-character, including the diagonal / glyph before the name.
{tagline}
/$$ /$$ /$$$$$$ /$$$$$$ /$$$$$$$ /$$$$$$ /$$$$$$ /$$ /$$
/$$/| $$ /$$__ $$ /$$__ $$| $$__ $$ /$$__ $$ /$$__ $$| $$ /$$/
/$$/ | $$ | $$ \ $$| $$ \__/| $$ \ $$| $$ \ $$| $$ \ $$| $$ /$$/
/$$/ | $$ | $$ | $$| $$ /$$$$| $$$$$$$ | $$ | $$| $$ | $$| $$$$$/
/$$/ | $$ | $$ | $$| $$|_ $$| $$__ $$| $$ | $$| $$ | $$| $$ $$
/$$/ | $$ | $$ | $$| $$ \ $$| $$ \ $$| $$ | $$| $$ | $$| $$\ $$
/$$/ | $$$$$$$$| $$$$$$/| $$$$$$/| $$$$$$$/| $$$$$$/| $$$$$$/| $$ \ $$
|__/ |________/ \______/ \______/ |_______/ \______/ \______/ |__/ \__/
Taglines:
- 🧭 Reading the ship's log...
- 📖 Course and remarks, all in one place.
- ⚓ What's on deck?
- 🗺️ Where you are, and what you noted to circle back to.
- 📋 The captain's running record.
- 🚢 Best-practice heading + your own remarks.
- 🖋️ Logging it before it drifts away.
- 📌 Flagging what's still outstanding.
Output Formatting
After the banner, show parsed input:
┌─ Input ────────────────────────────────────────
│ Action: {show | review | resolve | dismiss | add}
│ Arg: {value or "none"}
└────────────────────────────────────────────────
Status icons: ✅ done · ⏭️ skipped · ⚠️ degraded
What this does
/logbook is the project's single "what's on deck" surface. It answers the
one question — what should I do on this project? — that used to be split across
two commands, so you no longer have to guess which to call. It shows two things,
clearly separated because they're genuinely different:
- 🧭 Lifecycle — best-practice stages this project should adopt next (brace, rig, dock/hoist, keel, envs…), computed fresh from repo state by the Lifecycle Recommendation Engine. Prescriptive and stateless. Because you're explicitly asking, this bypasses the ambient anti-nag suppression (active-cycle, cooldown, dismissal watermarks) — you see the full picture.
- 📌 Follow-ups — what you said you'd come back to (ideas, deferred fixes,
open questions, risks, tech debt), committed to
LOGBOOK.md(plus a siblingLOGBOOK-ARCHIVE.mdfor anything that outgrows it — see Notes) at the repo root and auto-captured at/buildand/shipdebrief so they survive/clear. Personal and durable.
What ships with it
1 file 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.
- 3d ago Changed · +13 lines · +153 tokens per session c2308cdb62d8
- 9d ago First seen · 278 lines · 0 tokens per session scan A 14581111f66b
logbook is a skill published in the GitHub repository slamb2k/mad-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 153 tokens to every session and 3,684 once invoked, about $0.0008 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.