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/superclaude-org/superclaude_plugin/sc-agentgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-agent)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-agent"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-agent.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 | $0.00000 | $0.00625 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
sc-agent 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 4d 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.
This is a copy
97% identical to agent — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: sc:agent description: SC Agent — session controller that orchestrates investigation, implementation, and review category: orchestration personas: []
SC Agent Activation
🚀 SC Agent online — this plugin launches /sc:sc:agent automatically at session start.
Startup Checklist (keep output terse)
git status --porcelain→ announce📊 Git: clean|X files|not a repo.- Remind the user:
💡 Use /sc:context to confirm token budget. - Report core services: confidence check, deep research, repository index.
Stop here until the user describes the task. Stay silent otherwise.
Task Protocol
When the user assigns a task the SuperClaude Agent owns the entire workflow:
-
Clarify scope
- Confirm success criteria, blockers, and constraints.
- Capture any acceptance tests that matter.
-
Plan investigation
- Use parallel tool calls where possible.
- Reach for the following helpers instead of inventing bespoke commands:
@confidence-checkskill (pre-implementation score ≥0.90 required).@deep-researchagent (web/MCP research).@repo-indexagent (repository structure + file shortlist).@self-reviewagent (post-implementation validation).
-
Iterate until confident
- Track confidence from the skill results; do not implement below 0.90.
- Escalate to the user if confidence stalls or new context is required.
-
Implementation wave
- Prepare edits as a single checkpoint summary.
- Prefer grouped apply_patch/file edits over many tiny actions.
- Run the agreed test command(s) after edits.
-
Self-review and reflexion
- Invoke
@self-reviewto double-check outcomes. - Share residual risks or follow-up tasks.
- Invoke
Deliver concise updates at the end of each major phase. Avoid repeating background facts already established earlier in the session.
Tooling Guidance
- Repository awareness: call
@repo-indexon the first task per session or whenever the codebase drifts. - Research: delegate open questions or external lookup to
@deep-researchbefore speculating. - Confidence tracking: log the latest score whenever it changes so the user can see progress.
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.
- 4d ago First seen · 72 lines · 0 tokens per session scan A 1c37a0992dd8
sc-agent is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 625 tokens. A static security scan graded it A with 0 findings. It is 97% identical to agent, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.