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 agentmods add skills/spillwavesolutions/wiki_ticket_sdd/work-tracknpx skills add SpillwaveSolutions/wiki_ticket_sdd --skill work-trackgit clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sddWrote 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/spillwavesolutions/wiki_ticket_sdd/work-track)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/work-track"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/work-track.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.00043 | $0.00812 |
| Opus 5 | $0.00022 | $0.00406 |
| Sonnet 5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
work-track 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 yesterday.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work tracking
Every request that produces work gets worklog items FIRST — add them before
starting, move them in_progress → done as the work happens (the
UserPromptSubmit and Stop hooks enforce this). Unrecorded work is invisible work.
All state changes go through bin/worklog. Never edit .work/*.jsonl by
hand or with shell redirects (invariant 15.4) — the CLI's append() is the
only writer.
Add an item
bin/worklog add "<title>" --body "<readable description>" \
[--level epic|story|task|subtask] \
[--kind feature|bug|ops|triage] [--milestone v0.6.0] \
[--priority P0-P3] [--parent <ulid>] [--labels a,b]
Every item gets a --body (spec §13.4). One to three sentences a junior
dev or a PM can read in the ticket: what the work is and why it matters. No
ULIDs, no repo jargon in the reading path — the sync marker carries
provenance, the body carries meaning. A ticket whose body is only a worklog
id is a policy violation. Fix gaps with worklog update <ulid> --body "...".
Taxonomy rules (spec 5.4): epics are feature or ops only — kind is free
at story/task/subtask; bugs may float free of any epic (--parent optional).
--milestone goes on leaves (story and below); an epic's milestone derives
from its children. Unclassified work defaults to kind:triage — classify
deliberately, don't guess. --type is a deprecated alias (bug →
task/bug); prefer --level/--kind.
Unplanned discoveries
Work discovered mid-flight ("we also need to…", a bug found while doing something else) MUST be recorded BEFORE doing the work:
bin/worklog add "<title>" --unplanned --discovered-during <current-item-ulid>
--unplanned requires --discovered-during (spec 5.4).
Update / close
bin/worklog update <ulid> [--status todo|in_progress|blocked] \
[--kind feature|bug|ops|triage] [--milestone v0.6.0] \
[--priority P0-P3] [--add-label a] [--del-label b]
bin/worklog close <ulid> --status done|cancelled [--resolution "..."]
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.
- yesterday Changed 8cfea9b1e0cb
- 5d ago First seen · 75 lines · 43 tokens per session scan A b9a342d80dec
work-track is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 812 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…