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 i9wa4/dotfiles --skill logbookgit clone --depth 1 https://github.com/i9wa4/dotfilesWrote 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/i9wa4/dotfiles/logbook)<a href="https://agentmods.dev/skills/i9wa4/dotfiles/logbook"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/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/i9wa4/dotfiles/logbook"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/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.00106 | $0.00434 |
| Opus 5.5 | $0.00042 | $0.00174 |
| Sonnet 5.5 | $0.00021 | $0.00087 |
| Haiku 4.5 | $0.00011 | $0.00043 |
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 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.
What it actually says
Logbook
Owns local Markdown artifact creation, discovery, reuse, and lifecycle.
A logbook entry is a local Markdown file (mkmd). It remains the canonical
task source throughout the work, including after a delivery copy is prepared.
Route claude.ai's /artifacts feature to artifact-design.
Follow the active runtime/session language policy or explicit request. This skill does not define its own output language defaults.
1. Workflow
- If the requester supplied an artifact path, use that path as canonical.
- If no path was supplied, use Local Markdown Artifacts to discover work-start or resume candidates before creating a file.
- Reuse one matching active artifact for the same repo, branch, task, and purpose; create a separate file only for a genuinely separate purpose.
- If durable state is needed and no path exists, create a markdown artifact
with the cwd-independent
mkmdcontract in the local markdown reference. - Keep updating the canonical local artifact as task state. For human-facing Markdown, follow the readability guidance in the same reference. A request for a readable document does not authorize external publication.
2. References
For explicitly requested Gist delivery only, follow Secret-Gist Delivery.
What ships with it
14 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.
- evals/eval.yaml 496 B
- evals/tasks/negative-trigger-1.yaml 411 B
- evals/tasks/negative-trigger-2.yaml 523 B
- evals/tasks/positive-trigger-1.yaml 536 B
- evals/tasks/positive-trigger-2.yaml 461 B
- evals/tasks/positive-trigger-3.yaml 498 B
- evals/tasks/positive-trigger-4.yaml 550 B
- evals/tasks/positive-trigger-5.yaml 504 B
- evals/tasks/positive-trigger-6.yaml 653 B
- references/gist-delivery.md 4.2 KB
- references/local-markdown.md 9.9 KB
- scripts/mkmd 2.6 KB
- scripts/validate-gist-delivery-contract.sh 9.1 KB runs code
- scripts/verify-gist-delivery 3.0 KB
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 Changed · -2 lines · -2 tokens per session 1c7f7cbaf555
- 1mo ago First seen · 50 lines · 108 tokens per session scan A 76b4c0ef6c47
logbook is a skill published in the GitHub repository i9wa4/dotfiles (12 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 434 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
A local email tool for reading, searching, sorting, and tagging mail stored on the computer. It uses notmuch to index messages and afew to apply tags and suggest filtering rules.
handoff
Save state at the end of a session, or resume from the last one. Triggers "wrapping up", "running out of context", "done for today", "continue where we left off", "resume".
taskgo
Maintains a private Git-backed personal project and task control repository using concise current Markdown, derived Git history, ADRs, and status synchronization. Use when tracking tasks, updating project status (STATUS.md), managing ADRs, synchronizing tracker state, handing tasks to agents, or generating…
herdr
Use when the user mentions herdr or is working inside a herdr pane and wants to save/restore a pane layout, change herdr's theme, prefix or other preferences on this host only, start or check on an agent in another herdr pane, add, turn off or open a herdr plugin (file viewer, keybindings), or asks why the herdr…
create-handoff
Save the session's durable half as a memory file (save-memory), then write the perishable half -- the handoff prompt for the next session -- to a well-known place in the /.ai-memory repository and push it, so the next session, local or in the cloud, can pick the work up with read-handoff or pop-handoff and nobody has…
resume-from-chat-history
A recovery workflow for continuing a Kiro coding chat after it breaks or is lost by reading the saved session files on disk.