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/executenpx skills add skullninja/coco-workflow --skill executegit 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.00039 | $0.00366 |
| Opus 5 | $0.00019 | $0.00183 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
execute 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.
What it actually says
Coco Execute Skill
This skill delegates to the /coco:execute command, which implements the full 15-step TDD execution loop with PR workflow, AI code review, and issue tracker bridge sync.
When to Use
- Implementing a feature that has been imported into the coco tracker as an epic
- Executing tasks from a
specs/{feature}/tasks.mdthat has been converted to tracked tasks - Any multi-session work where dependency tracking matters
Alternatives
- For single-issue hotfixes or quick changes, use the
hotfixskill instead - For autonomous execution until epic completion, use
/coco:loop
Execution
Run the /coco:execute command. It handles:
- Pre-execution gate (tracker + issue tracker verification)
- Dependency-aware task selection via
coco-tracker ready - Issue branch creation (if
pr.enabled) - Issue tracker bridge (start: "In Progress")
- TDD implementation (RED -> GREEN -> verify)
- Pre-commit validation (UI change detection)
- Commit with issue key traceability
- PR creation with issue ID (if
pr.enabled) - AI code review via
code-revieweragent - Review-fix loop (max 3 iterations)
- PR merge (if
pr.enabled) - Tracker task close
- Issue tracker bridge (complete: "Done" at PR merge)
- Acceptance criteria verification
- Next task check (loop or report completion)
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 · 40 lines · 39 tokens per session scan A 552e492c18e7
execute is a skill published in the GitHub repository skullninja/coco-workflow (7 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 366 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
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…
council-implement
Execute a Carmack Council plan task by task. Use when explicitly asked to implement a plan, do a "council implement", "carmack implement", "council build", or invoke /council-implement. Reads the output of /council-plan and builds each task sequentially, loading the relevant expert's reference document per task.…