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/rube-de/cc-skills/full-taskgit 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/full-task)<a href="https://agentmods.dev/commands/rube-de/cc-skills/full-task"><img src="https://agentmods.dev/badge/commands/rube-de/cc-skills/full-task.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.02070 |
| Opus 5 | $0.00019 | $0.01035 |
| Sonnet 5 | $0.00008 | $0.00414 |
| Haiku 4.5 | $0.00004 | $0.00207 |
Grade C, and why
full-task scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
6. Clean up branch state: `[ -n "$BRANCH_SLUG" ] && rm -rf ".dev/cdt/$BRANCH_SLUG"` How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE: Coordinator only. You MUST NOT use Edit, Write, or NotebookEdit tools on source code, test files, or project docs. All implementation, testing, review, and documentation MUST be delegated to teammates via SendMessage. If you find yourself about to edit a file, STOP and delegate to the appropriate teammate instead. 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.
/full-task — Complete Workflow
Target: $ARGUMENTS
Two-phase orchestration: plan team → user approval → dev team. One team per session, so plan team must be fully cleaned up before dev team starts.
Phase 1: plan-team Phase 2: dev-team
┌───────────────────────────┐ ┌───────────────────────────┐
│ Lead (You) │ │ Lead (You) │
│ ├── architect [tm] │ plan.md │ ├── developer [tm] │
│ ├── product-manager [tm] │──────→ │ ├── code-tester [tm] │
│ └── researcher [sa] │ │ ├── qa-tester [tm] │
└───────────────────────────┘ │ ├── reviewer [tm] │
▲ │ └── researcher [sa] │
User Approval └───────────────────────────┘
[tm] = teammate (Agent Team) [sa] = subagent
The plan-team / dev-team labels above are role names; the actual team names created by the workflow are scoped per run as plan-<branch-slug>-<timestamp> and dev-<branch-slug>-<timestamp> to avoid collisions on the global ~/.claude/teams/ namespace, where branch-slug is the current branch name with / replaced by -.
Step 0: Git Check
- Run
git fetch origin - Ensure you are on
mainormaster— if not, rungit checkout main(ormaster, whichever exists) - Suggest a branch name based on the task (e.g.
feat/rate-limiting) - Run
git checkout -b <branch> origin/<default-branch>to create the feature branch from the latest remote default branch - Run
git pullto ensure up-to-date
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.
- 4d ago First seen · 160 lines · 39 tokens per session scan C 91302e80e80c
full-task is a command published in the GitHub repository rube-de/cc-skills (10 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,070 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
init
Initialize agent-harness model routing for your Claude tier (subscription or API).
doctor
Health check for greatcto. Shows pipeline state, missing artefacts, hook status, last run per agent, and permission-denied tail.
review
12-angle code review + skeptical triage (3-round + arbiter) for security/reliability P0/P1 findings, OR traceability tree. Default: review current branch vs main. --deep: triage ALL P0/P1 angles (not just security). With trace : render REQ → IMPL → TEST tree for impact analysis. Creates or closes gate:code for…
ccr
CCR (Compressed Context with Retrieval) — recall the full original of context that greatcto compressed/filtered out, by its short id. The retrieval half of the compression layer.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.