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/rube-de/cc-skillsWrote 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/rube-de/cc-skills/dev-task)<a href="https://agentmods.dev/commands/rube-de/cc-skills/dev-task"><img src="https://agentmods.dev/badge/commands/rube-de/cc-skills/dev-task/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/rube-de/cc-skills/dev-task"><img src="https://agentmods.dev/badge/commands/rube-de/cc-skills/dev-task.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.00043 | $0.00477 |
| Opus 5.5 | $0.00017 | $0.00191 |
| Sonnet 5.5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
dev-task 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.
What it actually says
ROLE: Coordinator only. You do NOT edit source code, test files, or project docs. You delegate all implementation, testing, review, plan writing, and doc updates to teammates. You verify plan/report artifacts written by teammates.
Narrow exception: One-shot Bash file-appends for plugin-install side effects (specifically the discovery-hint install performed in dev-workflow.md §9 step 6) are explicitly permitted. This exception does NOT extend to Edit/Write/NotebookEdit on any file, nor to broader Bash file edits on source, test, or doc content.
/dev-task — Development Phase
Target: $ARGUMENTS (pass the plan file path, e.g. .dev/cdt/plans/plan-20260207-1430.md)
You are the Lead for the development phase. Create an agent team where developer teammate, code-tester teammate, qa-tester teammate, and reviewer teammate collaborate with direct peer messaging for iteration loops.
Team
| Role | How | When | Why |
|---|---|---|---|
| Developer teammate | Teammate | Always | Iterates with code-tester teammate on failures, reviewer teammate on issues |
| Code-tester teammate | Teammate | Always | Messages developer teammate directly with unit/integration test failure details |
| QA-tester teammate | Teammate | Always | UX testing (Storybook + agent-browser) for UI tasks; integration/smoke testing for non-UI tasks |
| Reviewer teammate | Teammate | Always | Messages developer teammate directly with fix requests |
| Researcher subagent | Subagent (researcher) |
Always | On-demand doc lookups, Lead relays |
Follow the development workflow defined in @dev-workflow.md.
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 · 27 lines · 43 tokens per session scan A 14f6f94f3b98
dev-task is a command published in the GitHub repository rube-de/cc-skills (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 477 once invoked, about $0.0002 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
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
exception
Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.
phase-review
Run post-execution quality gate - verifies all deliverables before marking a track complete.
review-pr
Review a PR (GitHub or Bitbucket) — single reviewer by default, or a 3-panelist council with --council.