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/skullninja/coco-workflow/tasksnpx skills add skullninja/coco-workflow --skill tasksgit clone --depth 1 https://github.com/skullninja/coco-workflowWhat 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.00032 | $0.02296 |
| Opus 5 | $0.00016 | $0.01148 |
| Sonnet 5 | $0.00006 | $0.00459 |
| Haiku 4.5 | $0.00003 | $0.00230 |
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 2d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coco Tasks Skill
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts, then run cross-artifact consistency analysis.
When to Use
- Generating a task list as part of the coco pipeline
- Called by
/coco:phase(Step B) or/coco:planning-session tactical - When a tasks.md is needed in
specs/{feature}/before tracker import
Prerequisites: design.md must exist. If missing, use the design skill first.
Legacy fallback: If design.md doesn't exist, check for spec.md + plan.md as legacy artifacts and load both.
Setup
- Read
.coco/config.yamlforproject.specs_dir(default:specs). - Determine the current feature by:
- Checking the current git branch name
- Looking for the matching directory in
{specs_dir}/{branch-name}/ - Or from conversation context if a feature was recently discussed
- Load design documents from
{specs_dir}/{feature}/:- Required: design.md (user stories, tech stack, structure, API contracts, research decisions)
- Optional: data-model.md (entities, if generated separately)
- Legacy fallback: If
design.mddoesn't exist, loadspec.md+plan.md+data-model.md+contracts/+research.mdas legacy artifacts
- Load the tasks template from
.coco/templates/tasks-template.mdif it exists, otherwise use${CLAUDE_PLUGIN_ROOT}/templates/tasks-template.md.
Execution
1. Extract Context
- From design.md: tech stack, libraries, project structure, user stories with priorities (P1, P2, P3...), API contracts, research decisions
- From data-model.md (if exists): entities, map to user stories
Legacy mode (if loading spec.md + plan.md instead):
- From plan.md: tech stack, libraries, project structure
- From spec.md: user stories with priorities
- From data-model.md, contracts/, research.md (if exist): entities, endpoints, decisions
2. Generate Tasks
Organize tasks by user story. Every task MUST use this format:
- [ ] [TaskID] [P?] [Story?] Description with file path
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.
- 2d ago First seen · 211 lines · 32 tokens per session scan A 2cbb5e54291b
tasks is a skill published in the GitHub repository skullninja/coco-workflow (7 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 2,296 once invoked, about $0.0002 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
project-butler
Project memory workflow for init/upgrade, profile-aware setup, end session, normal/full close, file organization, document archiving, language switching, versioned update logs, rule review, status, wiki sync, and context recovery. Use for /project-butler, setup/初始化, foundation setup, profile setup, end session/收工…
effort-estimate
When the user needs accurate effort estimates for tasks, features, or projects. Use when the user says "how long will this take," "effort estimate," "estimate this," "scope this," "size this," "time estimate," "sprint planning," or when planning work. Unlike generic estimates, this skill calibrates against YOUR actual…
council-review
Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js)…
council-plan
Architect a feature with the Carmack Council before writing code. Use when explicitly asked to plan a feature, do a "council plan", "carmack plan", or invoke /council-plan. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo…
test-architect
Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write…
spec-writer
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this…