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 atman-33/workhub --skill create-work-loggit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/create-work-log)<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="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.00068 | $0.00746 |
| Opus 5 | $0.00034 | $0.00373 |
| Sonnet 5 | $0.00014 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
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 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.
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; agit log --authorfilter. When omitted, use each repo'sgit 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 --shortfor 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.
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.
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 First seen · 76 lines · 68 tokens per session scan A 9bcafa8661d0
create-work-log is a skill published in the GitHub repository atman-33/workhub (2 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. 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.
Other skills, from other repositories
continue
Autonomous work — find and execute ready tasks.
missive
Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.
pr
A command for managing pull requests on GitHub or Bitbucket Server. A pull request is a request for other developers to review and merge changes into a project branch.
work-story
Work a user story end to end — fetch the ticket, plan (with approval), implement, verify the applicable gates, self-review, open the PR, and update the tracker. Use when given an issue key like PROJ-1234, ENG-42, or.
shiploop
Self-improving multi-agent harness: wraps N git sub-repos as one workspace, dispatches named tickets to cheap-floor headless agents that escalate once on failure, promoting lessons into CLAUDE.md. Use when working in or scaffolding a meta-repo workspace (sub-folders each own .git; root has scripts/ + queue/tickets.md…
gh
GitHub API access and project management automation for the hallucination-detector repo. Uses octokit with proxy-aware client for all GitHub operations — issues, PRs, labels, milestones, Projects V2. No gh CLI required.