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/jpicklyk/task-orchestrator/work-summarynpx skills add jpicklyk/task-orchestrator --skill work-summarygit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote 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/jpicklyk/task-orchestrator/work-summary)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/work-summary"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/work-summary.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 | $0.00110 | $0.04082 |
| Opus 5 | $0.00055 | $0.02041 |
| Sonnet 5 | $0.00022 | $0.00816 |
| Haiku 4.5 | $0.00011 | $0.00408 |
Grade A, and why
work-summary 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Summary — Current (v3)
Attention-first project dashboard. The default (lean) mode answers four questions — what's moving, what's stuck, what's next, what's queued — in a bounded view (~45 lines) regardless of workspace size. The exhaustive inventory is available as an explicit mode, not the default: mature workspaces accumulate hundreds of terminal items, and rendering them all buries the actionable content.
Supplement the data with brief observations only when there is a genuine anomaly or actionable insight.
Step 0 — Mode Selection
$ARGUMENTS |
Mode |
|---|---|
| empty | Lean (default) |
the literal word full |
Full Inventory |
the literal word all |
Multi-Project — one condensed section per known project root |
| anything else | Scoped — resolve to a UUID via query_items(operation="search", query=$ARGUMENTS, limit=5); prefer the best-matching root or container item; if ambiguous, present matches via AskUserQuestion |
Step 0.5 — Project Scope Resolution
Before running Lean, Full, or Multi-Project mode, resolve the project rootId:
- Check session context for a rootId injected by the SessionStart hook.
- Otherwise, read
.taskorchestrator/config.yaml's top-levelproject.rootIdfield (a file read, not an MCP call). - If no rootId is found by either path, behavior is exactly as before this feature existed — every call below runs unscoped (whole-DB), and no
ancestorId/anchorIdparam is passed. This is the common case for single-project workspaces.
When a rootId is known, Lean and Full mode calls pass it as ancestorId="<rootId>" — except the overview calls, which use anchorId="<rootId>" (all noted inline below). Scoped mode is unaffected — it already resolves its own scope UUID per invocation via FTS.
Lean Mode (default)
Data collection (all parallel)
query_items(operation="overview", excludeTerminal=true)— non-terminal roots with theirchildCountsrole roll-ups only.includeChildrenis deliberately omitted: it is a no-op on the anchored (project-scoped) path — the anchored overview never returns per-child arrays, onlychildCounts— and unnecessary on the global path, since the step-5 queue-list is the canonical source for individual children. AddanchorId="<rootId>"when a rootId is known, to anchor the overview to this project. Detecting an older server: MCP servers silently ignore unknown parameters (they return200with the full unfiltered payload) rather than rejecting them — so a server predatingexcludeTerminalwill not error. Detect the no-op by inspecting the payload: if any returned root hasrole: "terminal"AND itschildCountsshow only terminal descendants (noqueue/work/review/blocked), the filter was not applied. Note the qualifier: a current server intentionally retains a terminal-role root that still has non-terminal descendants (it is active work parked under a done container), so a terminal root with open descendants is expected, not evidence of an old server. When the no-op is detected, (a) drop client-side only those terminal roots whosechildCountsshow no open descendants during enrichment, and (b) if the response is alsotruncated: true, re-issue withlimit=<total>(still passinganchorIdif known) so non-terminal roots in the tail (e.g. active containers) are not silently dropped — a truncated unfiltered payload can hide real workstreams. Headline counts never come from this payload regardless (see the role-total queries below), so correctness holds either way; this only recovers the workstream/backlog completeness the filter was meant to guarantee.get_context()— health-check: active items, blocked items, stalled items, claim summary. AddancestorId="<rootId>"when known.get_context(mode="session-resume", since="<now minus 48h, ISO 8601>")— recent role transitions (the "where did I leave off" signal). AddancestorId="<rootId>"when known — but note the known limitation:recentTransitionsis NOT scoped byancestorIdeven when passed; it always reflects the whole tree, not just this project.get_next_item(limit=5, includeDetails=true)— ranked recommendations with parentId/tags. AddancestorId="<rootId>"when known.query_items(operation="search", role="queue", limit=100)— the canonical source for queue children. Group its rows byparentIdto get each workstream's "next up" (the queue children the anchored overview omits); each row carriesparentId,depth,priority, andtype/tags.totalgives the true queued count. AddancestorId="<rootId>"when known. Exclude shelves from the headline: subtract rows whosetypeor tag iscontainerorproject— a freshly-created container/anchor sits inqueuerole until its first advance and would otherwise inflateN queued. Iftotalexceeds the returned page (queue backlog >100), note the headline count is approximate.query_items(operation="search", role="terminal", limit=1)— readtotalfor the true terminal count. AddancestorId="<rootId>"when known.
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.
- 4d ago First seen · 212 lines · 110 tokens per session scan A 7283ea62e808
work-summary is a skill published in the GitHub repository jpicklyk/task-orchestrator (205 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 4,082 once invoked, about $0.0006 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.
Other skills, from other repositories
file-todos
File-based todo and task tracking in the todos/ directory. Use when creating, triaging, listing, or managing todo files, tracking work items, managing the backlog, converting PR comments to tracked tasks, or checking todo status and dependencies.
branch-surgery-pr-split
Split oversized or mixed-concern branches into smaller, reviewable PR stacks with safety refs, topology selection, parity audits, and merge sequencing. Use when a PR or branch is too large, difficult to review, mixed across concerns, conflict-prone, or needs to be decomposed without losing net changes.
workpackage-management
Use when performing workpackage actions: start, pause, complete, delete, defer, reorder, update progress, or check dependencies. Not for reading WP history or definitions.
cf-workpackage
Manage workpackage lifecycle — view status, list, create, start, pause, track progress, validate, complete, or delete. Use when the user mentions workpackages, asks to start or pause work, wants progress updates, or needs to change workpackage state.
cf-plan
Manage and view the development plan — status, progress, blockers, phases, and next steps. Use when the user asks about plan status, needs next-step recommendations, wants to create or modify the plan, or asks about phases and milestones.
do-it
Turn the current discussion into a task step and implement it — adds step to task file, updates spec if needed, then implements with review-fix loop.