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.
git clone --depth 1 https://github.com/ddunnock/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/commands/ddunnock/claude-plugins/tasks)<a href="https://agentmods.dev/commands/ddunnock/claude-plugins/tasks"><img src="https://agentmods.dev/badge/commands/ddunnock/claude-plugins/tasks/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/commands/ddunnock/claude-plugins/tasks"><img src="https://agentmods.dev/badge/commands/ddunnock/claude-plugins/tasks.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.00008 | $0.02446 |
| Opus 5.5 | $0.00003 | $0.00978 |
| Sonnet 5.5 | $0.00002 | $0.00489 |
| Haiku 4.5 | $0.00001 | $0.00245 |
Grade A, and why
tasks 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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tasks
Generate SMART-validated implementation tasks from plans + constitution + memory files.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Usage
/tasks # Generate tasks from all plans
/tasks plan.md # Generate from specific plan
/tasks --all # Force regenerate all tasks
/tasks --status # Show task summary without generating
Memory Directives
Load these directive files for task generation:
Always loaded:
constitution.md- Global principles, section references for taskstesting.md- Test coverage requirements (80% minimum)git-cicd.md- Git workflow and CI/CD standards
Project-specific (detected: Python ≥3.11, Poetry, MCP SDK):
python.md- Python standards, Pyright strict, ruff lintingsecurity.md- API key management, input validation
SMART Acceptance Criteria Validation
Every acceptance criterion must pass SMART validation:
| Element | Requirement | Fail Condition |
|---|---|---|
| Specific | Clear, concrete action | "properly", "correctly", "fully", "appropriately" |
| Measurable | Objective verification | No command/metric/file check defined |
| Achievable | Single task scope | Requires other tasks to complete first |
| Relevant | Ties to task purpose | No trace to plan/requirement/ADR |
| Time-bound | Immediate verification | Requires external delays or human approval |
SMART Strictness Level
| Level | Behavior | When to Use |
|---|---|---|
| Strict | Block until criterion rewritten | Critical tasks, security-related |
| Standard | Flag for review, allow with warning | Default for most tasks |
| Relaxed | Log finding only | Exploratory/research tasks |
Selected for this project: Standard
Criterion Format
**Acceptance Criteria**:
- [ ] File `src/knowledge_mcp/store/qdrant_store.py` exists
Verification: `ls src/knowledge_mcp/store/qdrant_store.py`
SMART: S✓ M✓ A✓ R✓ T✓
- [ ] QdrantStore class passes type checking
Verification: `poetry run pyright src/knowledge_mcp/store/`
SMART: S✓ M✓ A✓ R✓ T✓
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 · 380 lines · 8 tokens per session scan A 0b5690d54b64
tasks is a command published in the GitHub repository ddunnock/claude-plugins (14 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 2,446 once invoked, about $0.0000 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-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.