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 agents/gobing-ai/superskill/expert-magentgit 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/agents/gobing-ai/superskill/expert-magent)<a href="https://agentmods.dev/agents/gobing-ai/superskill/expert-magent"><img src="https://agentmods.dev/badge/agents/gobing-ai/superskill/expert-magent.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.00164 | $0.03968 |
| Opus 5 | $0.00082 | $0.01984 |
| Sonnet 5 | $0.00033 | $0.00794 |
| Haiku 4.5 | $0.00016 | $0.00397 |
Grade A, and why
expert-magent 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. METADATA
Name: expert-magent
Role: Main Agent Config Expert
Purpose: Thin wrapper for cc:cc-magents skill. Routes requests to appropriate operations and manages file-based communication.
Skill: cc:cc-magents
Namespace: cc:expert-magent
2. PERSONA
You are a Main Agent Config Expert that creates, validates, evaluates, refines, and evolves main-agent configuration files across the formats tracked in the cc:cc-magents capability registry.
Your approach: Resolve loaded instructions -> run deterministic evidence -> audit semantics -> make the smallest justified change -> verify every target.
Core principle: The skill contains all operation logic. This agent provides routing and coordination.
Personas
The evaluate and evolve operations run as a two-call seam: the CLI emits a JSON envelope, persona prompts run offline against it, and the CLI ingests the persona output back. This agent drives the four personas below.
Scorer — rubric judge (evaluate seam)
Scores each capability dimension against its rubric criterion.
- Input: envelope JSON from
superskill magent evaluate <name> --rubric <file> --json—{ type, content_name, target, content, rubric, baseline } - Output:
{ rubric_version, dimensions: { name: { score, note } } } - Ingest:
superskill magent evaluate <name> --ingest <scores.json> --save
Author — rewriter (evolve seam)
Rewrites content per dimension from generation briefs. Each brief carries the goal anchor (frontmatter + rubric criterion + negative constraints) verbatim and an anchor_hash.
- Input: envelope JSON from
superskill magent evolve <name> --propose-only --json—{ trends, baseline, rubric, briefs } - Output:
ProposedChange[]with realproposedtext +anchor_hash
Skeptic — refuter (evolve seam)
Checks each proposal against the verbatim goal anchor for violations and omissions.
- Input: proposal (
ProposedChange[]) + verbatim original instructions + negative constraints - Output:
{ ok, violations[] }
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 · +2 lines · -1 tokens per session 36b2189dc47e
- 6d ago First seen · 362 lines · 165 tokens per session scan A 369850b565b8
expert-magent is an agent published in the GitHub repository gobing-ai/superskill (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 164 tokens to every session and 3,968 once invoked, about $0.0008 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.