Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rube-de/cc-skills/plugin install plugin-devWrote 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/skills/rube-de/cc-skills/develop)<a href="https://agentmods.dev/skills/rube-de/cc-skills/develop"><img src="https://agentmods.dev/badge/skills/rube-de/cc-skills/develop.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.1 | $0.00051 | $0.00822 |
| Opus 5 | $0.00026 | $0.00411 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
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 7d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Developer Workflow
Implement skill development issues through iterative planning, TDD-governed implementation, and review cycles.
When to Use
- Implementing a GitHub issue that creates or modifies skills, plugins, agents, or hooks
- Issue requires TDD-governed phases (baseline → implement → verify)
- Work involves SKILL.md frontmatter, workflow references, agent prompts, or hook scripts
When NOT to Use
- General code changes unrelated to skill/plugin authoring
- Quick validation or auditing — use
/plugin-devinstead - Scaffolding a new plugin from scratch — use
/plugin-dev:createinstead
Quick Reference
| Phase | Action | Exit Condition |
|---|---|---|
| 0. Setup | MUST create feature branch | On feature branch (NOT main/master) |
| 1. Context | Read issue + detect skill files | Requirements clear, skill files noted |
| 2. Plan | Draft implementation plan | Plan complete |
| 3-4. Validate | Gemini review loop (max 5) | APPROVED status |
| 4.5. Baseline (RED) | TODO: #163 — capture baseline behavior | Baseline captured (or skipped pending #163) |
| 5-7. Implement (GREEN) | Write minimal skill addressing failures | All tasks done + criteria met + tests passing + validation passing |
| 7.5. Verify (REFACTOR) | TODO: #163 — compare against baseline | Benchmark passes (or skipped pending #163) or escalated |
| 8-9. Review | Council review (max 3) | APPROVED status |
| 10. Finalize | Commit + PR | PR created |
| 11. Cleanup | Clean temps, delete branch | Branch deleted after merge |
Consultant Scaling
| Change Size | Criteria | Consultants |
|---|---|---|
| Trivial | <10 lines, no logic changes | Skip review → Phase 10 |
| Small | 1-2 files, simple logic | council:gemini-consultant only |
| Medium | 3-5 files, moderate complexity | council:gemini-consultant + council:codex-consultant |
| Large | 6+ files, architectural impact | /council skill |
Skill File Detection
During Phase 1, detect and note these skill-related files for domain-specific handling:
SKILL.md— Skill activation definitions (YAML frontmatter + instructions)references/*.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.jsonvia${CLAUDE_PLUGIN_ROOT}/scripts/...)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 75 lines · 51 tokens per session scan A ed66cc2f41de
develop is a skill published in the GitHub repository rube-de/cc-skills (10 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 822 once invoked, about $0.0003 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 skills, from other repositories
test-strategy
Coverage-design method for qa-engineer — pyramid ratios per archetype, equivalence/boundary/property case selection, mutation score as the real coverage signal, and a flake-quarantine policy. Turns "coverage is 90%" (a number with no method) into a defensible test plan. Emits TEST-STRATEGY-{slug}.md, which the QA gate…
quant-validation
The methods a financial-ML result has to survive before it is evidence — purged cross-validation with an embargo, triple-barrier labelling, sample uniqueness under overlapping labels, fractional differentiation, meta-labelling, and multiple-testing correction. Written because the invariants were required of…
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
deep-plan
Creates detailed, sectionized, TDD-oriented implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
clean-code
This skill should be used when the user asks to "refactor code", "review code quality", "apply clean code principles", "check for code smells", "improve code design", "do a clean code review", "apply SOLID principles", "fix naming", "reduce complexity", or when performing the refactor phase of a TDD cycle.