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 gobing-ai/superskill/plugin install ccWrote 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/gobing-ai/superskill/cc-commands)<a href="https://agentmods.dev/skills/gobing-ai/superskill/cc-commands"><img src="https://agentmods.dev/badge/skills/gobing-ai/superskill/cc-commands/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/skills/gobing-ai/superskill/cc-commands"><img src="https://agentmods.dev/badge/skills/gobing-ai/superskill/cc-commands.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.00047 | $0.02371 |
| Opus 5.5 | $0.00019 | $0.00948 |
| Sonnet 5.5 | $0.00009 | $0.00474 |
| Haiku 4.5 | $0.00005 | $0.00237 |
Grade A, and why
cc-commands 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.
How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-commands: Universal Command Creator
Create and manage slash commands that work across multiple agent platforms.
Overview
This skill provides a complete pipeline for slash command development
(evolve is a separate longitudinal loop with snapshot-backed accept/reject):
| Operation | Purpose | CLI |
|---|---|---|
| scaffold | Create new command from template | superskill command scaffold |
| validate | Check structure and frontmatter | superskill command validate |
| evaluate | Score quality via two-call seam (envelope-out → Scorer → ingest-in) | superskill command evaluate |
| refine | Fix issues and improve quality | superskill command refine |
| evolve | Propose/accept longitudinal improvements via two-call seam (envelope-out → Author → Skeptic → Judge → ingest-in) | superskill command evolve |
When to Use
Use for:
- Creating a new slash command from scratch
- Validating command structure and frontmatter
- Evaluating command quality across 5 rubric dimensions
- Refining commands based on evaluation feedback
- Planning longitudinal improvement proposals
Quick Start
# Scaffold a new command
superskill command scaffold my-command --output ./commands
# Validate command structure
superskill command validate ./commands/my-command.md
# Evaluate: envelope-out → Scorer → ingest-in
superskill command evaluate ./commands/my-command.md --rubric <file> --json
# ... Scorer persona scores offline ...
superskill command evaluate ./commands/my-command.md --ingest <scores.json> --save
# Refine command based on evaluation
superskill command refine ./commands/my-command.md --auto --save
# Evolve: envelope-out → Author → Skeptic → Judge → ingest-in
superskill command evolve my-command --propose-only --json
# ... Author rewrites, Skeptic refutes, Judge selects ...
superskill command evolve my-command --ingest <proposal.json> --accept <id>
Core Principles
Fat Skills, Thin Wrappers
All coding agents support agent skills now, but slash commands and subagents are not universally supported. So we MUST follow these principles:
What ships with it
10 files 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.
- agents/openai.yaml 104 B
- metadata.openclaw 336 B
- references/command-examples.md 2.2 KB
- references/evaluation-framework.md 5.4 KB
- references/evolution-protocol.md 2.4 KB
- references/frontmatter-reference.md 4.1 KB
- references/platform-compatibility.md 5.1 KB
- references/red-flags.md 6.5 KB
- references/troubleshooting.md 1.1 KB
- references/workflows.md 30 KB
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 · 256 lines · 47 tokens per session scan A 210371af06e6
cc-commands is a skill published in the GitHub repository gobing-ai/superskill (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 47 tokens to every session and 2,371 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…