worklog

A command for keeping daily Markdown worklog entries, which are plain-text notes about completed work, decisions, risks, and next actions.

In plain words
What is it for?
Creating or opening today's entry and viewing completed items from the last seven days.
Why use it?
It keeps session progress in dated files so recent work and unfinished tasks are easier to review.

Command

Install

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.

agentmods
npx agentmods add commands/milindgaharwar/fettle/worklog
Clone the repo
git clone --depth 1 https://github.com/MilindGaharwar/fettle
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00421
Opus 5 $0.00005 $0.00211
Sonnet 5 $0.00002 $0.00084
Haiku 4.5 $0.00001 $0.00042

Measured 2d ago against content hash 9fbce3081850, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

worklog 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 2d 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.

Origin

This is a copy

92% identical to fettle-worklog — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/worklog.md · 57 lines

What it actually says

Manage the daily worklog at .fettle/worklog/YYYY-MM-DD.md.

Procedure

  1. Parse arguments. Default action is "today" (show or create today's entry).

    • view — show last 7 days of completed items
    • create — create today's template if missing
    • today — open today's entry (create if needed)
  2. For "view": Read the last 7 files in .fettle/worklog/ (named YYYY-MM-DD.md, so lexical order is date order) and present their "Completed" sections.

  3. For "create" or "today":

    • Check if .fettle/worklog/YYYY-MM-DD.md exists
    • If not, create the template
    • Read and present the file to the user
    • Offer to help fill in the "Completed" section from this session's work
  4. Auto-populate from session context:

    • Review files modified this session
    • Review commits made
    • Review decisions discussed
    • Suggest entries for the "Completed" and "Decisions" sections

Template

# Worklog: YYYY-MM-DD

## Completed
- [what shipped or was accomplished]

## Decisions
- [key choices made and why]

## Blockers / Risks
- None (or describe blockers)

## Next Actions
- [what carries forward to tomorrow]

Notes

  • The worklog gate (Stop hook) advisories if no entry exists for today
  • Enable enforcement: [gates.worklog] enabled = true in .fettle.toml
  • Worklogs are gitignored by default (in .fettle/)
  • To track in git: add .fettle/worklog/ to your repo
Changes

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.

  1. 2d ago First seen · 57 lines · 10 tokens per session scan A 9fbce3081850

Subscribe to this mod's changes

worklog is a command published in the GitHub repository MilindGaharwar/fettle (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 10 tokens to every session and 421 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to fettle-worklog, differing in 7 lines, and is treated as a copy.