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/commands/skullninja/coco-workflow/status)<a href="https://agentmods.dev/commands/skullninja/coco-workflow/status"><img src="https://agentmods.dev/badge/commands/skullninja/coco-workflow/status/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/skullninja/coco-workflow/status"><img src="https://agentmods.dev/badge/commands/skullninja/coco-workflow/status.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.00017 | $0.00649 |
| Opus 5.5 | $0.00007 | $0.00260 |
| Sonnet 5.5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
status 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Setup
- If
$ARGUMENTScontains an epic ID, use it. Otherwise, find the most recent open epic:
Pick the most recent non-closed epic from the output.coco-tracker epic-status
Execution
1. Get Epic State
coco-tracker epic-status {epic-id}
coco-tracker list --json --epic {epic-id}
2. Categorize Tasks
Group tasks by status:
- Running (
in_progress): Currently being worked on - Available (
pending, not blocked): Ready to start - Blocked (
pending, has unresolved blockers): Waiting on dependencies - Completed: Done
3. File Ownership Map
For each running task, read owns_files from metadata (if present) and display:
File Ownership
==============
Task {id} ({title}):
- {file pattern 1}
- {file pattern 2}
Unclaimed:
- {remaining file patterns}
4. Parallel Opportunities
Identify tasks that could run in parallel right now:
Parallel Opportunities
======================
Available tasks with no file conflicts:
1. {task title} (no overlap with running tasks)
Cannot parallelize:
- {task title} (blocked by {blocking-tasks})
5. Worktree / Parallel Status
Read loop.parallel.enabled from .coco/config.yaml. If parallel execution is enabled:
Parallel Execution
==================
Mode: {enabled | disabled}
Max agents: {max_agents}
Active Worktrees:
- worktree-{task-id}: {task title} ({status: running | completed | failed})
Branch: {issue-branch}
PR: #{pr-number} ({review status})
Merge Queue:
- PR #{N}: {task title} (awaiting review)
Recently Completed:
- {task-id}: {title} -- merged via PR #{N}
If parallel execution is not enabled, skip this section.
6. Dependency Graph
Show the dependency tree with status indicators:
Dependency Graph
================
[x] Phase 1: Setup
[x] Phase 2: Foundational
+-- [>] Phase 3: US1 (in_progress)
+-- [ ] Phase 4: US2 (available)
+-- [~] Phase 5: Polish (blocked by 3, 4)
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 · 113 lines · 17 tokens per session scan A a7a0806b6fde
status is a command published in the GitHub repository skullninja/coco-workflow (8 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 649 once invoked, about $0.0001 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 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-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-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-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.