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 Jakeintech/waybill/plugin install waybillWrote 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/jakeintech/waybill/log)<a href="https://agentmods.dev/skills/jakeintech/waybill/log"><img src="https://agentmods.dev/badge/skills/jakeintech/waybill/log/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/jakeintech/waybill/log"><img src="https://agentmods.dev/badge/skills/jakeintech/waybill/log.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.00132 | $0.01964 |
| Opus 5.5 | $0.00053 | $0.00786 |
| Sonnet 5.5 | $0.00026 | $0.00393 |
| Haiku 4.5 | $0.00013 | $0.00196 |
Grade A, and why
log 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Work
Record work in the ledger at the moment it happens. Follow the storage and
schema rules from the ledger skill (skills/ledger/SKILL.md in this
plugin, with references/schema.md and references/methodology.md). Read
both references before writing entries.
Use the engine for every write — invoke it as
"${CLAUDE_PLUGIN_ROOT}/bin/waybill" <command>.
If ${WAYBILL_HOME:-$HOME/.waybill}/config.json does not exist, run ledger
initialization first (see the ledger skill).
Determine the mode
- Opening — the user is about to start a task ("I'm starting PLAT-482").
- Closing — a task just shipped ("log this, the PR merged").
- Pinning — the user asserts this session's spend belongs to a key ("pin this session to PLAT-482", "unpin").
- Mining — the user asks to process pending sessions, or unmined files
exist in
pending-sessions/when another log request comes in (mention the count, offer to mine them).
Opening a task (pre-registration — the important one)
- Ask the user for their without-Claude estimate as a range in hours,
before any work with Claude begins — once, with the one-line why (it is
what makes later time-saved claims credible). If they decline, open the
entry without an estimate (
estimate_without_claude_hours: null, nopre_registered): the item stays fully logged at facts tier, and any later time-saved claim for it will be judgment tier. Never press twice, and never backfill. - If Atlassian MCP tools are connected, fetch the issue to fill
points,epic_key,epic_name,sprint. Otherwise ask only for what's needed and leave the restnull. - Build the
openedentry body (noid) withpre_registered: true,claude_role: "none", empty artifacts, and append it:"${CLAUDE_PLUGIN_ROOT}/bin/waybill" append --stream ledger --event '<json>' --commit. The engine seals the estimate in a SHA-256 escrow automatically and refuses backdated pre-registration. - Confirm in one line, mentioning the seal the first time:
Opened PLAT-482 (5 pts) — estimate 10–16h, sealed in escrow.
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 · 159 lines · 132 tokens per session scan A bd2a0793d2c6
log is a skill published in the GitHub repository Jakeintech/waybill (1 stars, last pushed 1mo ago), licensed MIT. It adds 132 tokens to every session and 1,964 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
glyph
Render an answer as ASCII art plus semantic emojis inline with no setup questions: one render per reply, verdict first. Use for any answer with shape: status, inventories, audits, budgets, comparisons, rankings, pipelines, 'what is using X', or any ad-hoc 'show me X visually' ask. Not for definitions, conceptual…
prompt-focus
Shows where your attention went from your own Claude Code and Codex prompts: projects, hours and re-typed asks over 20 weeks, as a local counts-only HTML report. Use when asking where your focus goes.
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
onboarding-and-offboarding
Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner…
14-email-marketing
Dung khi can xay chuoi email hoac Zalo OA gui theo kich ban — welcome series, nurture, promotion, win-back: phan tep, luong automation, subject line, tan suat gui, A/B test va KPI open/click. Kich hoat khi user nhac 'email marketing', 'chuoi email tu dong', 'welcome email', 'email nurture', 'broadcast Zalo OA', 'co…