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 instructions/promptwheel-ai/logbook/agents-mdgit clone --depth 1 https://github.com/promptwheel-ai/logbookWrote 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/instructions/promptwheel-ai/logbook/agents-md)<a href="https://agentmods.dev/instructions/promptwheel-ai/logbook/agents-md"><img src="https://agentmods.dev/badge/instructions/promptwheel-ai/logbook/agents-md.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.1 | $0.00908 | $0.00908 |
| Opus 5 | $0.00454 | $0.00454 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
logbook AGENTS.md 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
logbook — agent notes
Single-file zero-dep CLI (bin/logbook.mjs) + MCP wrapper (mcp/server.mjs).
Run tests: npm test (root) and cd mcp && npm test (behavioral, drives the
real server over stdio). Inside this repo use node bin/logbook.mjs, not
npx — npm prefers the same-name local package and shadows the registry.
Release invariants (regression-tested — keep all of them green)
- A fresh self-run on THIS repo reports 0 suppression events. The
detector must never flag its own regex tables or comments about skip
APIs (diff
+/-prefix is stripped beforeisMention; call-syntax idioms inside comments are prose). - Bump
EXTRACTOR_VERSIONwhenever detector precision changes — the events.jsonl cache is rejected on mismatch, so old ledgers can't mask a fix. Verify fresh and upgraded-cache self-runs agree. - Public JSON is cache-invariant:
--json(and MCPlogbook_query) byte-identical with and withoutLOGBOOK_NO_CACHE=1. Events are stamped withxvat birth incollectEvents, not at write time. - Cache freshness is the exact current ordered non-merge Git window, never “newest cached SHA is present.” Merges can introduce older-dated side commits; reuse rows by immutable full SHA, scan missing SHAs, then restore Git's canonical order.
initwrites the ordered read → bounded path-context → verify workflow with neutral--by MODELattribution and creates the CLAUDE.md@AGENTS.mdbridge; exact released blocks migrate, user-edited blocks are never touched.DEFAULT_MAXis the single source for the commit window — the ledger cache gate inloadEventsdepends on it.- Never turn "unmeasurable" into clean: a failed diff scan sets
A.degraded(surfaced in LOGBOOK.md); a failedgit grepin audit throws instead of reporting clean. - All repository-controlled Markdown and agent-facing audit values go through
the single
sanitizeContextTextimplementation. Rendering must never mutateevents.jsonl,--json, or query output. - Generated artifacts use atomic per-file replacement and one shared stamped
record.
logbook doctoris read-only and must fail stale/tampered bundles or shadowing wiring without repairing them while it checks.
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.
- 5d ago First seen · 69 lines · 908 tokens per session scan A bd9c59f1a900
logbook AGENTS.md is an instructions file published in the GitHub repository promptwheel-ai/logbook (3 stars, last pushed 1mo ago), licensed MIT. It adds 908 tokens to every session, about $0.0045 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 instructions, from other repositories
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).