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 commands/skullninja/coco-workflow/standupgit 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.00021 | $0.00629 |
| Opus 5 | $0.00010 | $0.00315 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
standup 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
$ARGUMENTS can be an epic ID to scope the standup, or empty for all active epics.
Setup
- Read
.coco/config.yamlfor project configuration.
Execution
1. Gather Tracker State
Get all epics and tasks:
coco-tracker list --json
If $ARGUMENTS specifies an epic, filter to that epic. Otherwise, include all non-closed epics.
2. Gather Git Activity
Get recent commits (last 24 hours):
git log --oneline --since="24 hours ago" --format="%h %s (%ar)"
Get current branch:
git branch --show-current
3. Gather Issue Tracker State (if configured)
Read issue_tracker.provider from config:
If "linear": Use mcp__plugin_linear_linear__list_issues to get issues for active projects with recent updates.
If "github":
- Use
gh issue listto get recent issue activity. - If
github.use_projectsis true: also querygh project item-list {project_number} --owner {github.owner} --format jsonto show board column status alongside tracker state.
If "none": Skip.
4. Produce Standup Report
Output a structured standup:
## Standup: {YYYY-MM-DD}
### Done (last 24h)
- {task-id}: {title} -- {commit-hash} ({time ago})
{issue-key if available}
### In Progress
- {task-id}: {title} -- claimed {time ago}
Branch: {branch from metadata}
Issue: {issue-key from metadata}
### Blocked
- {task-id}: {title}
Waiting on: {dependency-id} ({dependency-title})
### Up Next
- {task-id}: {title} (next ready task per dependency order)
### Metrics
- Tasks completed (24h): {count}
- Commits (24h): {count}
- Active epics: {count} ({completed}/{total} tasks, {percent}% complete)
5. Issue Tracker Summary (if configured)
If an issue tracker is configured, append:
### Issue Tracker
- Open issues: {count}
- In Review: {count}
- Recently closed: {count in last 24h}
Rules
- If no active epics exist, report "No active epics. Start with
/coco:phaseor/coco:planning-session tactical." - If no activity in the last 24 hours, report "No activity in the last 24 hours" with current state.
- Keep the output scannable -- tables and bullet points, not prose.
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 · 97 lines · 21 tokens per session scan A e19a0a2ebdaf
standup is a command published in the GitHub repository skullninja/coco-workflow (7 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 629 once invoked, about $0.0001 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 commands, from other repositories
super-dev
Command "super-dev" from shangyankeji/super-dev, covering /super-dev (claude-code), 输入, super dev runtime contract, local knowledge contract and 首轮响应契约(首次触发必须执行).
super-dev-seeai
Command "super-dev-seeai" from shangyankeji/super-dev, covering /super-dev-seeai (claude-code), 输入, seeai 定位, 半小时时间盒 and 首轮输出模板.
implement
You are the phase dispatcher. Your job is to route implementation work to the correct phase agent with the right context.
retro
You are generating a retrospective report for a completed feature. Your job is to analyze git history and project artifacts to surface patterns, measure delivery quality, and suggest workflow improvements.
progress
You are generating a visual progress report showing which phases are complete, in-progress, or pending for the current feature.
commit
You are creating a conventional commit scoped to the current phase of work.