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/tlangridge/agent-swarm/task-managementnpx skills add tlangridge/agent-swarm --skill task-managementgit clone --depth 1 https://github.com/tlangridge/agent-swarmWrote 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/tlangridge/agent-swarm/task-management)<a href="https://agentmods.dev/skills/tlangridge/agent-swarm/task-management"><img src="https://agentmods.dev/badge/skills/tlangridge/agent-swarm/task-management.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.00026 | $0.00746 |
| Opus 5 | $0.00013 | $0.00373 |
| Sonnet 5 | $0.00005 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
task-management 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Management
Tasks are the primary unit of work in the swarm. Every piece of work should be tracked as a task.
Task Lifecycle
open -> in-progress -> done
\ /
-> blocked --------/
- open -- Available for pickup
- in-progress -- An agent is actively working on it
- blocked -- Work cannot continue (dependency unmet, error encountered)
- done -- Work completed and verified
Ownership Model
- If a PM is present, PM owns day-to-day board operations (create/assign/reprioritize/follow-up).
- Tech Lead keeps strategic oversight and intervenes for high-level decisions or risk correction.
- If no PM is present, lead handles board operations directly.
Task Commands
Viewing Tasks
swarm tasks - List all tasks
swarm tasks --mine - List your assigned tasks
swarm tasks --ready - List tasks ready for pickup (deps met, unassigned)
swarm tasks --status open - Filter by status
swarm task show <id> - Show task details
Creating Tasks (lead/creator)
swarm task create <title> --desc "description" --priority high --assign <name>
swarm task create <title> --depends id1,id2 --branch feature/xyz
Always include when creating tasks:
- A specific, actionable title (not "fix tests" but "Fix failing jest tests in server/services/task-board.test.ts")
--descwith: (1) what to do, (2) which files to modify, (3) acceptance criteria--priority(urgent/high/medium/low)--depends id1,id2if this task requires another task to finish first--assignto a specific agent when possible
Working on Tasks
swarm task pick <id> - Self-assign and start working
swarm task update <id> --branch <branch> - Link your branch
swarm task update <id> --pr <number> --pr-url <url> - Link a PR
swarm task update <id> --issue <number> --issue-url <url> - Link an issue
Completing Tasks
swarm task verify <id> <command> - Run verification (e.g., npm test)
swarm task done <id> --output "summary of what was produced"
swarm task fail <id> <reason> - Mark as blocked with reason
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.
- 5d ago First seen · 86 lines · 26 tokens per session scan A 562900f31bb7
task-management is a skill published in the GitHub repository tlangridge/agent-swarm (5 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 746 once invoked, about $0.0001 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…