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 skills add fergupa/claude_plugins --skill task-managementgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/task-management)<a href="https://agentmods.dev/skills/fergupa/claude_plugins/task-management"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/task-management/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/skills/fergupa/claude_plugins/task-management"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/task-management.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.00072 | $0.00879 |
| Opus 5.5 | $0.00029 | $0.00352 |
| Sonnet 5.5 | $0.00014 | $0.00176 |
| Haiku 4.5 | $0.00007 | $0.00088 |
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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Management
Tasks are tracked in a TASKS.md file that both you and the user can edit.
File Location
Always use TASKS.md in the current working directory.
- If it exists, read/write to it
- If it doesn't exist, create it with the template below
Format & Template
When creating a new TASKS.md, use this template:
# Tasks
## Active
<!-- Current tasks requiring action -->
## Journal Entries Due
<!-- JE prep, review, and posting tasks - ties to journal-entry-prep skill -->
## Waiting On
<!-- Blocked items: approvals, info from others -->
## Recurring - Month-End
<!-- Standard close tasks that repeat each period -->
## Someday
## Done
Task format:
- [ ] **Task title** - context, for whom, due date- Sub-bullets for additional details
- Completed:
- [x] ~~Task~~ (date)
How to Interact
When user asks "what's on my plate" / "my tasks":
- Read TASKS.md
- Summarize Active, Journal Entries Due, and Waiting On sections
- Highlight anything overdue or urgent
- Flag journal entries approaching close deadline
When user says "add a task" / "remind me to":
- Add to Active section with
- [ ] **Task**format - If the task is a journal entry, add to Journal Entries Due section instead
- Include context if provided (who it's for, due date, period)
When user says "done with X" / "finished X":
- Find the task
- Change
[ ]to[x] - Add strikethrough:
~~task~~ - Add completion date
- Move to Done section
When user asks "what am I waiting on":
- Read the Waiting On section
- Note how long each item has been waiting
When user says "close checklist" or "month-end status":
- Show all tasks in Journal Entries Due and Recurring - Month-End
- Summarize: how many done vs remaining
- List any blocked items from Waiting On that affect close
Journal Entry Integration
When the user works on journal entries using the journal-entry-prep skill, offer to:
- Track the JE as a task - Add to Journal Entries Due with entry type, amount, and period
- Track approvals - If the entry exceeds a threshold (e.g., >$250K needs CFO approval), add a Waiting On item for the approval
- Mark complete when posted - Move to Done with the posting date
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 109 lines · 72 tokens per session scan A e3c179741b40
task-management is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 879 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…