log-work

A work-log procedure that records each completed work segment in a dated Markdown file named WORKLOG/YYYYMMDD.md. Entries include the time, session, files read or created, results, and changed code files when relevant.

In plain words
What is it for?
Use it to append a top-level, timestamped section to the current day's work log after completing a segment of work.
Why use it?
It preserves a concise history of what was done and which files were involved. This makes later review or handoff easier.

Skill for Claude CodeCodex

Part of the workflow plugin — 4 skills, 1 agent shipped together

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 skills/pchalasani/claude-code-tools/log-work
Any agent
npx skills add pchalasani/claude-code-tools --skill log-work
Clone the repo
git clone --depth 1 https://github.com/pchalasani/claude-code-tools

Made for: Claude Code, Codex.

Or install workflow, the plugin that ships this one along with the rest of its 4 skills, 1 agent.

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00299
Opus 5 $0.00010 $0.00150
Sonnet 5 $0.00004 $0.00060
Haiku 4.5 $0.00002 $0.00030

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

Security

Grade A, and why

log-work 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 3d 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/workflow/skills/log-work/SKILL.md · 35 lines

What it actually says

log-work

  1. create the file WORKLOG/YYYYMMDD.md if it doesn't already exist.
  2. if the file exists, append a new TOP-LEVEL markdown section to it.
  3. When you add a section, follow this format for the section header, so it has HH:MM timestamp followed by suitable concise topic
# 13:45 Added feature xyz

In the log section include a CONCISE set of items such as the following (Not all may apply to all situations, use your judgement):

  • the session_id of the current session
  • any text/md file(s) you CREATED and their purpose
  • any text/md file(s) you READ as part of the current task
  • short description of what you just did, including any results you got
  • which code files were created/changed
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. 3d ago First seen · 35 lines · 19 tokens per session scan A 0a7ae5e2d3a1

Subscribe to this mod's changes

log-work is a skill published in the GitHub repository pchalasani/claude-code-tools (1,989 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 299 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

myagents-task-automation

让 Agent 建立 MyAgents Task 的完整产品心智模型,并创建、验证和治理需要持久追踪、独立 Session 或未来触发的工作:理解 Task 与立即执行/Record/Goal 的边界,以及 once/scheduled/recurring、Session routing、结束条件和 command Detector。用户提到创建 Task、定时、稍后、周期检查、持续关注、满足条件才处理时使用;普通立即执行、仅保存 Record 或明确要求 Goal Mode 的工作不使用。.

hAcKlyc/MyAgents · 112 tokens

luvus

Control Luvus through its local CLI and UHP. Use only for a line beginning with =target message, an explicit request naming Luvus, a request to delegate to a named live Luvus agent or pane, or an explicit Luvus operation involving sessions, workspaces, tabs, panes, agents, files, Git, DIFF, worktrees, tasks, leases…

RizRiyz/luvus · 177 tokens

apple-reminders

Manage Apple Reminders via the remindctl CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.

hAcKlyc/MyAgents · 41 tokens

apple-notes

Manage Apple Notes via the memo CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks to add a note, list notes, search notes, or manage note folders.

hAcKlyc/MyAgents · 54 tokens

notion

Notion workspace management via API — pages, databases, blocks.

furkangonel/cowrangler · 16 tokens

tmux-via-mcp

Use the tmux MCP tools to create sessions, shape layouts, run tracked commands, and automate interactive terminals when a real TTY or parallel panes are required.

bnomei/tmux-mcp · 39 tokens