A command that records a day's development work in Jira, a system for tracking software tasks and time spent on them.

Use it to log work for PROJ tickets by date, total hours, start time, lunch break, and change complexity.

It converts committed work into time entries while accounting for working hours, lunch, and the relative size of changes.

logwork — Command by jpeseWang

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/jpesewang/solo-dev-workflow/logwork

Clone the repo

git clone --depth 1 https://github.com/jpeseWang/solo-dev-workflow

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.02764
Opus 5	$0.00000	$0.01382
Sonnet 5	$0.00000	$0.00553
Haiku 4.5	$0.00000	$0.00276

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

Security

Grade A, and why

logwork scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -w "\nHTTP_CODE:%{http_code}" -X POST \

variants/team-jira/commands/logwork.md · 248 lines

How it starts

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

You are the assistant that logs work to Jira for the PROJ tickets worked on during the day in the Acme project (single Jira project: PROJ at your-domain.atlassian.net).

Purpose

At the end of the day, automatically log work to Jira for all tickets committed during the day, ensuring:

Total time = total_hours (default 8h)
Subtract the lunch break (default 12:30-13:30)
Distribute time by complexity (number of files changed, insertions/deletions)
Consecutive started timestamps (the next ticket starts right after the previous ticket ends)

Input

$ARGUMENTS — optional flags:

No arg → today, 8h, lunch 12:30-13:30, start 09:00
yesterday → the previous day
2026-04-27 → a specific date
--total=7h → override total hours
--start=10:00 → override start time
--lunch=12:00-13:00 → override lunch break

Examples:

/logwork → today, 8h, start 9:00
/logwork yesterday → yesterday, 8h
/logwork --total=6h --start=10:00 → today, 6h, start 10:00

Actions

STEP 0: Check task-state.json (priority before daily-report)

STATE_FILE=".claude/task-state.json"

if [ -f "$STATE_FILE" ]; then
  python3 -c "
import json
state = json.load(open('$STATE_FILE'))
done_unlogged = [t for t in state['tasks'] if t.get('status') == 'done' and not t.get('logged_time')]
active = [t for t in state['tasks'] if t.get('status') == 'active']

if done_unlogged:
    print('DONE_UNLOGGED=' + ','.join(t['ticket'] for t in done_unlogged))
if active:
    print('ACTIVE=' + ','.join(t['ticket'] + '(' + t['branch'] + ')' for t in active))
"
fi

If there is a done task without logged_time → tell the user: "[INFO] There are N tasks pushed but not yet logged. Run /push on each branch to log accurately, or continue with /logwork to log manually."
If there is an active task (not yet pushed) → tell them: "[INFO] Task $TICKET has been active since HH:MM. Run /push when done to log automatically."
If there is no state file or everything is already logged → continue the normal flow at STEP 1.

Read the full file on GitHub · 248 lines

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.

2d ago First seen · 248 lines · 0 tokens per session scan A 24744a1ea447

Subscribe to this mod's changes

logwork is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,764 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

speckit.auto

Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.

VisActor/VChart · 31 tokens

daily-priorities

Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).

DIGI-UW/OpenELIS-Global-2 · 0 tokens

logwork