What is create-work-log?

A tool that turns Git activity from configured repositories into a daily or weekly work log in Markdown. Git is a system that records changes to code, including who made them and when.

Use it to summarize completed changes, note work in progress, and record repositories with no activity for a chosen period.

It replaces memory-based status writing with a record of commits and uncommitted work across multiple repositories.

create-work-log — Skill for Claude Code by atman-33/workhub

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.

Any agent

npx skills add atman-33/workhub --skill create-work-log

Clone the repo

git clone --depth 1 https://github.com/atman-33/workhub

Made for: Claude Code.

Or install authoring, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/atman-33/workhub/create-work-log/github.svg)](https://agentmods.dev/skills/atman-33/workhub/create-work-log)

Your own site

<a href="https://agentmods.dev/skills/atman-33/workhub/create-work-log"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/create-work-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/atman-33/workhub/create-work-log"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/create-work-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 746 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00068	$0.00746
Opus 5.5	$0.00027	$0.00298
Sonnet 5.5	$0.00014	$0.00149
Haiku 4.5	$0.00007	$0.00075

Measured 1mo ago against content hash 9bcafa8661d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-work-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.

plugins/authoring/skills/create-work-log/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Work Log

Turn real git activity into a readable work log — Markdown, because the destination is typically an Obsidian vault or a chat paste, not a browser.

1. Resolve config

Read config.json next to this SKILL.md. If it doesn't exist, read config.example.json for the shape, ask the user for real values, then write config.json (git-ignored):

repos — absolute paths of repositories to scan.
outputDir — where logs are saved (e.g. an Obsidian vault folder).
gitAuthor — optional; a git log --author filter. When omitted, use each repo's git config user.name.

2. Determine the period

Default: today (--since 00:00). "Weekly" or an explicit range from the user overrides it. State the resolved period in the log header.

3. Collect activity — from git, not memory

Per configured repo:

git log --all --author=<author> --since=<start> --until=<end> --pretty='%h %s (%D)' for commits (all branches — feature-branch work counts).
git status --short for uncommitted work in progress, noted as such.
Skip repos with no activity; list them in one "no activity" line at the end.

Completion criterion: every configured repo was scanned; nothing in the log is inferred without a commit or a dirty file behind it.

4. Compose the log

Group by repo, then by theme (feature/fix/docs — the Conventional Commit prefixes make this mechanical). Write prose summaries in the user's conversation language; keep commit subjects verbatim. Structure:

# Work Log — <period>

## <repo name>
- <theme>: <1–2 line summary> (`abc1234`, `def5678`)
- In progress (uncommitted): <summary>

## Notes
<anything the user dictated to include — blockers, decisions, tomorrow's plan>

Before saving, ask the user one question: anything to add that git can't show (meetings, reviews, blockers)? Fold the answer into Notes — or skip the question when running unattended (e.g. from a scheduled routine) and note "auto-generated" in the header instead.

Read the full file on GitHub · 76 lines

Files

What ships with it

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

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.

1mo ago First seen · 76 lines · 68 tokens per session scan A 9bcafa8661d0

Subscribe to this mod's changes

create-work-log is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 746 once invoked, about $0.0003 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-03.

Claude Code Git and workflow Project management claude-code-plugin cross-platform desktop-app developer-tools obsidian

catchup

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

oliver-kriska/claude-elixir-phoenix · 48 tokens

backlog

Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…

umputun/cc-thingz · 96 tokens

create-work-log