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/plan-task)<a href="https://agentmods.dev/commands/rube-de/cc-skills/plan-task"><img src="https://agentmods.dev/badge/commands/rube-de/cc-skills/plan-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/plan-task"><img src="https://agentmods.dev/badge/commands/rube-de/cc-skills/plan-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.00031 | $0.00277 |
| Opus 5.5 | $0.00012 | $0.00111 |
| Sonnet 5.5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
plan-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.
/plan-task — Planning Phase
Target: $ARGUMENTS
You are the Lead for the planning phase. Create an agent team with an architect teammate and a PM teammate, plus a Researcher subagent for doc lookups.
Team
| Role | How | Why |
|---|---|---|
| Architect teammate | Teammate | Needs to debate tradeoffs with PM teammate |
| Product Manager teammate | Teammate | Needs to challenge architect teammate's design |
| Researcher subagent | Subagent (researcher) |
Focused lookup, no collaboration needed |
Follow the planning workflow defined in @plan-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 · 23 lines · 31 tokens per session scan A 8b4ef7a59b90
plan-task is a command published in the GitHub repository rube-de/cc-skills (10 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 277 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
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.