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.
git clone --depth 1 https://github.com/jpeseWang/solo-dev-workflowWrote 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/commands/jpesewang/solo-dev-workflow/logwork)<a href="https://agentmods.dev/commands/jpesewang/solo-dev-workflow/logwork"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/logwork/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.
<a href="https://agentmods.dev/commands/jpesewang/solo-dev-workflow/logwork"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/logwork.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02764 |
| Opus 5.5 | $0.00000 | $0.01106 |
| Sonnet 5.5 | $0.00000 | $0.00553 |
| Haiku 4.5 | $0.00000 | $0.00276 |
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 2mo 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 \ 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 day2026-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
donetask withoutlogged_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
activetask (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.
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.
- 2mo ago First seen · 248 lines · 0 tokens per session scan A 24744a1ea447
logwork is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 2mo 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.