Borrowing it
Nothing to install: this file belongs to knitli/codeweaver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/knitli/codeweaver/main/.claude/commands/tasks.mdgit clone --depth 1 https://github.com/knitli/codeweaverWrote 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/knitli/codeweaver/tasks)<a href="https://agentmods.dev/commands/knitli/codeweaver/tasks"><img src="https://agentmods.dev/badge/commands/knitli/codeweaver/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/knitli/codeweaver/tasks"><img src="https://agentmods.dev/badge/commands/knitli/codeweaver/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.00000 | $0.00620 |
| Opus 5.5 | $0.00000 | $0.00248 |
| Sonnet 5.5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
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.
This is a copy
92% identical to tasks — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description: Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).
User input:
$ARGUMENTS
-
Run
.specify/scripts/bash/check-prerequisites.sh --jsonfrom repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. -
Load and analyze available design documents:
- Always read plan.md for tech stack and libraries
- IF EXISTS: Read data-model.md for entities
- IF EXISTS: Read contracts/ for API endpoints
- IF EXISTS: Read research.md for technical decisions
- IF EXISTS: Read quickstart.md for test scenarios
Note: Not all projects have all documents. For example:
- CLI tools might not have contracts/
- Simple libraries might not need data-model.md
- Generate tasks based on what's available
-
Generate tasks following the template:
- Use
.specify/templates/tasks-template.mdas the base - Replace example tasks with actual tasks based on:
- Setup tasks: Project init, dependencies, linting
- Test tasks [P]: One per contract, one per integration scenario
- Core tasks: One per entity, service, CLI command, endpoint
- Integration tasks: DB connections, middleware, logging
- Polish tasks [P]: Unit tests, performance, docs
- Use
-
Task generation rules:
- Each contract file → contract test task marked [P]
- Each entity in data-model → model creation task marked [P]
- Each endpoint → implementation task (not parallel if shared files)
- Each user story → integration test marked [P]
- Different files = can be parallel [P]
- Same file = sequential (no [P])
-
Order tasks by dependencies:
- Setup before everything
- Tests before implementation (TDD)
- Models before services
- Services before endpoints
- Core before integration
- Everything before polish
-
Include parallel execution examples:
- Group [P] tasks that can run together
- Show actual Task agent commands
-
Create FEATURE_DIR/tasks.md with:
- Correct feature name from implementation plan
- Numbered tasks (T001, T002, etc.)
- Clear file paths for each task
- Dependency notes
- Parallel execution guidance
Context for task generation: $ARGUMENTS
The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.
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 · 70 lines · 0 tokens per session scan A 232e74969946
tasks is a command published in the GitHub repository knitli/codeweaver (12 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 620 tokens. A static security scan graded it A with 0 findings. It is 92% identical to tasks, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
ccc
CC Commander Hub — interactive menu derived from adventure JSON files. 450+ skills, 11 CCC domains, 80+ commands, 9 modes.
ccc-spawn
Plan and launch parallel Claude Code peers (quick, team, swarm or domain expert), each on its own branch and worktree with non-overlapping files, then track or stop them. Use when work splits into independent parts that should run in separate sessions.
ccc-improve
Run the continuous-improvement pipeline: scan GitHub and npm for new Claude Code tooling, score proposals, and approve or reject them in a local queue. Use when reviewing ecosystem findings or deciding what to adopt next.
ccc-linear
Show the Linear project board by status with a progress bar, pick an issue to start work on, or create a new issue, with every Linear write confirmed first. Use when you want to see or act on your Linear project from the session or the ccc CLI.
ccc-makeover
Score project health with X-Ray, apply the top recommendations in impact order with your OK for each, and show the before and after score. Use when you want the highest-impact project health fixes applied and measured.
ccc-office-hours
Stress-test a product idea before writing code through product, technical and user lenses, ending in BUILD IT, SIMPLIFY FIRST, RESEARCH MORE or KILL IT. Use when deciding whether a feature or product is worth building.