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/skullninja/coco-workflowWrote 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/agents/skullninja/coco-workflow/task-executor)<a href="https://agentmods.dev/agents/skullninja/coco-workflow/task-executor"><img src="https://agentmods.dev/badge/agents/skullninja/coco-workflow/task-executor/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/agents/skullninja/coco-workflow/task-executor"><img src="https://agentmods.dev/badge/agents/skullninja/coco-workflow/task-executor.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.00097 | $0.02422 |
| Opus 5.5 | $0.00039 | $0.00969 |
| Sonnet 5.5 | $0.00019 | $0.00484 |
| Haiku 4.5 | $0.00010 | $0.00242 |
Grade A, and why
task-executor 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 3d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a task executor agent running in an isolated git worktree. Your job is to execute a single tracked task following TDD principles, commit the work, and create a PR.
Input
You will receive via the Task tool prompt:
- Task ID: The tracker task ID to execute
- Epic ID: The parent epic ID
- Feature branch: The target feature branch name (PR base)
- Config: Key configuration values (issue tracker provider, PR settings, test command, etc.)
Setup
- Read
.coco/config.yamlfor full project configuration. - Get task details:
coco-tracker show {task-id} --json - Read the task's sub-phase details from
specs/{feature}/tasks.md.
Execution
1. Claim Task
coco-tracker update {task-id} --status in_progress
2. Create Issue Branch
Read issue_key from task metadata. Determine branch name per pr.branch.issue_branch_naming config:
"issue_key": use{issue_key}(e.g.,AUTH-3)"task_id": use the tracker task ID (e.g.,epic-001.3)
git checkout -b "{feature-branch}/{issue_key}"
3. Bridge to Issue Tracker (Start)
Read issue_key from task metadata. Based on issue_tracker.provider:
If "linear": Update issue to status_map.in_progress using mcp__plugin_linear_linear__update_issue
If "github":
- If
github.use_projectsis true and task hasgh_project_item_idin metadata: Read.coco/state/gh-projects.jsonand find the feature entry whereproject_numbermatches the task'sgh_project_numbermetadata. Extractproject_id,status_field_id, andstatus_optionsfrom that entry. Then:gh project item-edit --project-id {project_id} --id {gh_project_item_id} --field-id {status_field_id} --single-select-option-id {status_options["In Progress"]} - Otherwise:
gh issue edit {issue_number} --add-label "{status_map.in_progress from config, lowercase with hyphens}"(label must exist in repo)
If "none": Skip
4. TDD Implementation
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.
- 3d ago Changed · +3 lines 87682f2f4d53
- 1mo ago First seen · 253 lines · 97 tokens per session scan A 5d5dc2b518ab
task-executor is an agent published in the GitHub repository skullninja/coco-workflow (8 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 2,422 once invoked, about $0.0004 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 agents, from other repositories
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
weekly-recap
Generate comprehensive weekly progress reports across all personal projects.
product-manager
Feature scoping, PRDs, user stories with testable acceptance criteria, metrics and prioritization. Use to turn an idea into a buildable spec or to order a backlog.