agent

A session controller for a coding agent that guides investigation, implementation, and review from task start to finish.

In plain words
What is it for?
It helps clarify tasks, inspect a repository, research questions, plan tool use, and review completed changes.
Why use it?
It gives work a defined process, so important checks, constraints, and review steps are less likely to be missed.

Command

Install

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.

agentmods
npx agentmods add commands/superclaude-org/superclaude_framework/agent
Clone the repo
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_Framework
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 621 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00621
Opus 5 $0.00000 $0.00311
Sonnet 5 $0.00000 $0.00124
Haiku 4.5 $0.00000 $0.00062

Measured 2d ago against content hash e5271074a811, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • sc-agent — 97% identical, 4 lines differ
plugins/superclaude/commands/agent.md · 72 lines

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:agent automatically at session start.

Startup Checklist (keep output terse)

  1. git status --porcelain → announce 📊 Git: clean|X files|not a repo.
  2. Remind the user: 💡 Use /context to confirm token budget.
  3. 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:

  1. Clarify scope

    • Confirm success criteria, blockers, and constraints.
    • Capture any acceptance tests that matter.
  2. Plan investigation

    • Use parallel tool calls where possible.
    • Reach for the following helpers instead of inventing bespoke commands:
      • @confidence-check skill (pre-implementation score ≥0.90 required).
      • @deep-research agent (web/MCP research).
      • @repo-index agent (repository structure + file shortlist).
      • @self-review agent (post-implementation validation).
  3. 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.
  4. 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.
  5. Self-review and reflexion

    • Invoke @self-review to double-check outcomes.
    • Share residual risks or follow-up tasks.

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-index on the first task per session or whenever the codebase drifts.
  • Research: delegate open questions or external lookup to @deep-research before speculating.
  • Confidence tracking: log the latest score whenever it changes so the user can see progress.

Read the full file on GitHub · 72 lines

Changes

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.

  1. 2d ago First seen · 72 lines · 0 tokens per session scan A e5271074a811

Subscribe to this mod's changes

agent is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,856 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 621 tokens. 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-30.