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/developgit clone --depth 1 https://github.com/rube-de/cc-skillsWhat 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.00011 | $0.00567 |
| Opus 5 | $0.00005 | $0.00283 |
| Sonnet 5 | $0.00002 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
develop 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plugin-dev:develop — Skill Developer Workflow
Implement a GitHub issue for skill development using the skill-developer workflow.
Usage
/plugin-dev:develop #160
/plugin-dev:develop owner/repo#160
Behavior
This command activates the develop skill which runs the full skill-developer workflow:
setup → context → plan → validate → [baseline] → implement → [verify] → review → finalize
Core Phases
- Phase 0: Setup — create feature branch
- Phase 1: Context — read issue, detect skill files
- Phase 2: Plan — draft implementation plan
- Phase 3-4: Validate — Gemini review loop
- Phase 5-7: Implement — write code, verify criteria
- Phase 8-9: Review — council review
- Phase 10: Finalize — commit, push, create PR
- Phase 11: Cleanup — clean temps
TDD Extension Points (planned — see #163)
- Phase 4.5 (RED): Baseline capture — run test prompts without skill changes (currently skipped)
- Phase 5-7 (GREEN): Implementation constrained by baseline failures (active when baseline exists)
- Phase 7.5 (REFACTOR): Verify + benchmark — compare against baseline, iterate on loopholes (currently skipped)
First Action
- Read
plugins/plugin-dev/skills/develop/SKILL.mdto load the skill activation context - Read
plugins/plugin-dev/skills/develop/references/WORKFLOW.mdand follow it phase-by-phase, passing$ARGUMENTSas the raw issue reference (WORKFLOW.md Phase 0 handles all parsing to extractREPOandISSUE_NUM)
Arguments
$ARGUMENTS— GitHub issue reference in any format:#123,owner/repo#123, or issue URL
Skill File Detection
The workflow automatically detects skill-related files for domain-specific handling:
SKILL.md— Skill activation definitionsreferences/*.md— Workflow reference files (e.g.,references/WORKFLOW.md)agents/*.md— Agent/subagent definitionshooks/hooks.json— Hook config (declares hook types, matchers, and script references)scripts/— Hook scripts (executables referenced byhooks.json)
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 · 57 lines · 11 tokens per session scan A 827cd3cbe2f8
develop is a command published in the GitHub repository rube-de/cc-skills (10 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 567 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
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
init
First-run teamctl onboarding — from no-teamctl-installed to a running supervised team in one conversation.
compose-stack
Compose a sequenced Intelligence Stack Plan for a sovereign person. Analyzes their Genius Profile + Freedom Path + stated priorities + life stage, then sequences which of the 9 layers activate first, second, third. Produces a 90-day sprint plan for building their full intelligence stack. For humans with Genius Profile…
init
Initialize agent-harness model routing for your Claude tier (subscription or API).
pm-board
Open the great-pm board — a native, zero-dependency project board (hybrid stage×status Kanban + artifact panels + verdict metrics) served from the great-pm plugin itself. Self-contained, no npm packages.
new
Starts a new end-to-end need (preflight, team, spawn OR).