log-work

log-work is a skill for Claude Code from pchalasani/claude-code-tools. It costs 108 tokens per session (307 once invoked), scanned A, original, MIT.

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 Code

Written for Claude Code: shipped in a Claude Code plugin.

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

Good fit Use it to append a top-level, timestamped section to the current day's work log after completing a segment of work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pchalasani/claude-code-tools/log-work
About the project

pchalasani/claude-code-tools is a collection of command-line tools, skills, agents, hooks, plugins, and commands for improving work with Claude Code, Codex-CLI, and similar coding agents. It is used by developers who want reusable productivity features and workflows for terminal-based AI coding assistants. The catalogue entries are components of, or extensions for, these coding-agent workflows.

pchalasani/claude-code-tools · 2,020 stars · on GitHub

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

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

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.

agentmods badge for log-work

README.md
[![agentmods](https://agentmods.dev/badge/skills/pchalasani/claude-code-tools/log-work/github.svg)](https://agentmods.dev/skills/pchalasani/claude-code-tools/log-work)
Your own site
<a href="https://agentmods.dev/skills/pchalasani/claude-code-tools/log-work"><img src="https://agentmods.dev/badge/skills/pchalasani/claude-code-tools/log-work/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.

agentmods 80×15 button for log-work

Your own site · 80×15
<a href="https://agentmods.dev/skills/pchalasani/claude-code-tools/log-work"><img src="https://agentmods.dev/badge/skills/pchalasani/claude-code-tools/log-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 307 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00108 $0.00307
Opus 5.5 $0.00043 $0.00123
Sonnet 5.5 $0.00022 $0.00061
Haiku 4.5 $0.00011 $0.00031

Measured 7d ago against content hash 08e61ad14dcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 7d 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 · 37 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. 7d ago Changed · +2 lines · +89 tokens per session 08e61ad14dcf
  2. 1mo 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 (2,020 stars, last pushed 5d ago), licensed MIT. It adds 108 tokens to every session and 307 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

delegation

Delegates independent work to worker agents through the Task tool, choosing between the explore scout and the ml, biology, physics, chemistry and data specialists, writing a self-contained brief for a worker that cannot see the conversation, setting boundaries on files and compute, using two independent annotators…

synthetic-sciences/openscience · 118 tokens

mcptoon

Compress MCP tool discovery with the mcptoon CLI. Trigger when a session has a large MCP tool catalog (many servers/tools), when the user mentions token cost, tool discovery, mcptoon, or asks to list/call MCP tools efficiently. Also route here when the user says the MCP tool list is too large, the agent context window…

activeing123/mcptoon · 523 tokens

meeting-transcript-to-action-items

Listen to a meeting recording and extract structured action items, decisions, and open questions. Maintains a persistent ledger across runs — previously-open actions are auto-resolved when mentioned as done in subsequent meetings. Outputs actions.csv (importable to Linear/Asana/Notion) + recap.md (paste into Slack).…

skrun-dev/skrun · 90 tokens

text-processing

Transform, filter, sort, and analyze text using sed, awk, sort, uniq, cut, tr, wc, and other text processing tools. Use when the user asks to find and replace text in files, extract columns from data, count lines or words, sort and deduplicate output, reformat delimited data, perform field-based calculations, or build…

bug-ops/zeph · 79 tokens

scheduling

Scheduling across time zones: confirm times in the attendee's own zone, use IANA zone names, mind DST edges, buffers and calendar etiquette. Use when booking meetings or calls with people in other zones.

damianvtran/local-operator · 44 tokens

email

Manage emails via Himalaya CLI. Use when the user wants to read, send, search, or organize emails. Triggers on "email", "inbox", "send email", "check mail", "reply to", "forward", or mentions of Gmail, Outlook, iCloud, Proton Mail.

lvndry/jazz · 63 tokens