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/gobing-ai/superskill/magent-refinegit clone --depth 1 https://github.com/gobing-ai/superskillWrote 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/gobing-ai/superskill/magent-refine)<a href="https://agentmods.dev/commands/gobing-ai/superskill/magent-refine"><img src="https://agentmods.dev/badge/commands/gobing-ai/superskill/magent-refine.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.00010 | $0.00611 |
| Opus 5 | $0.00005 | $0.00305 |
| Sonnet 5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
magent-refine 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magent Refine
Wraps cc:cc-magents skill.
Run evaluation, apply deterministic structural fixes (missing fields, type coercion, whitespace),
then re-evaluate. Magents are frontmatter-optional plain markdown, so --auto is usually a clean
no-op on their body: it surfaces low-scoring dimensions but does not perform semantic rewrites.
The invoking agent owns those edits under the cc:cc-magents workflow.
When to Use
- Improve magent config quality after scaffolding
- Apply low-risk structural fixes and surface semantic work
- Preview fixes without writing with
--dry-run
Arguments
| Argument | Description | Default |
|---|---|---|
<nameOrPath> |
Configuration name or path to its .md file | (required) |
--auto |
Skip interactive prompts (auto-apply fixes) | false |
--save |
Persist the evaluation to the evaluation store | false |
--dry-run |
Preview classified fixes and projected delta without writing | false |
--target |
Target platform | claude |
Examples
# Refine a config (evaluate + structural fixes + re-evaluate)
/cc:magent-refine ./CLAUDE.md
# Auto-refine without prompts
/cc:magent-refine ./CLAUDE.md --auto --save
# Preview fixes without writing
/cc:magent-refine ./CLAUDE.md --dry-run
Refinement Contract
Follow cc:cc-magents workflows § "Main-Agent Evaluation and Refinement". Freeze requested layout and critical boundaries; fix contradictions and dead commands first; delete no-ops and sediment; collapse duplicate owners; move rarely needed depth to live authoritative links; add only missing non-inferable guidance. Preserve safety and verification inline on targets that do not receive rule modules.
After semantic edits, assemble every target and re-run strict validation plus evaluation. Compare
every dimension with baseline, not only the aggregate. Do not claim --auto applied a body change
that it only suggested.
Implementation
Pass $ARGUMENTS to the underlying skill for processing.
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 Changed · +7 lines 8648c1284eb4
- 6d ago First seen · 67 lines · 10 tokens per session scan A 4246f705c202
magent-refine is a command published in the GitHub repository gobing-ai/superskill (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 10 tokens to every session and 611 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.