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 sequenzia/claude-plugins --skill simple-task-managementgit clone --depth 1 https://github.com/sequenzia/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/sequenzia/claude-plugins/simple-task-management)<a href="https://agentmods.dev/skills/sequenzia/claude-plugins/simple-task-management"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/simple-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/sequenzia/claude-plugins/simple-task-management"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/simple-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.01320 |
| Opus 5.5 | $0.00029 | $0.00528 |
| Sonnet 5.5 | $0.00014 | $0.00264 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
simple-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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simple Task Management
Transform specification documents (PRDs, Technical Specifications, Design Documents) into structured task lists organized under named missions that can be executed systematically.
Core Workflow
1. Document Analysis
Parse the specification document to extract:
- Explicit requirements: Stated features, functionality, acceptance criteria
- Implicit requirements: Technical considerations, infrastructure needs, error handling
- Constraints: Technology choices, performance requirements, compatibility needs
- Scope boundaries: What is and isn't included in the specification
Read the source document thoroughly. Identify section headings, numbered requirements, user stories, acceptance criteria, and technical specifications. Note any cross-references between sections.
2. Task Decomposition
Break requirements into atomic tasks with these characteristics:
| Characteristic | Description |
|---|---|
| Single responsibility | Each task addresses one specific piece of functionality |
| Independence | Tasks can be worked on without coordination where possible |
| Clear boundaries | Well-defined start and end conditions |
| Testable | Verifiable completion criteria exist |
Decomposition process:
- Identify each distinct requirement in the specification
- Determine if the requirement is atomic or needs splitting
- Create task entries with unique IDs (TASK-001, TASK-002, etc.)
- Ensure each task maps to specific specification sections
3. Dependency Mapping
Identify blocking dependencies between tasks:
- Blocking dependencies: Task B cannot start until Task A completes
Populate the dependencies array with task IDs this task depends on. Calculate blocked_by (incomplete dependencies) and blocks (tasks depending on this one).
4. Priority Calculation
Score and prioritize tasks based on:
- Dependency depth: Tasks unblocking many others rank higher
- Complexity: Use T-shirt sizing (XS, S, M, L, XL)
- Risk level: Higher uncertainty = higher priority (do risky things early)
- Business value: When indicated in specification
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 · 182 lines · 72 tokens per session scan A 491836e630b1
simple-task-management is a skill published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 72 tokens to every session and 1,320 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.
remove
Remove a deployed framework or addon from the current workspace.