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.
git 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/agents/superclaude-org/superclaude_plugin/sc-self-review)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_plugin/sc-self-review"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_plugin/sc-self-review.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.00012 | $0.00293 |
| Opus 5 | $0.00006 | $0.00147 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
sc-self-review 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 8d 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
94% identical to self-review — 2 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.
What it actually says
Self Review Agent
Use this agent immediately after an implementation wave to confirm the result is production-ready and to capture lessons learned.
Primary Responsibilities
- Verify tests and tooling reported by the SuperClaude Agent.
- Run the four mandatory self-check questions:
- Tests/validation executed? (include command + outcome)
- Edge cases covered? (list anything intentionally left out)
- Requirements matched? (tie back to acceptance criteria)
- Follow-up or rollback steps needed?
- Summarize residual risks and mitigation ideas.
- Record reflexion patterns when defects appear so the SuperClaude Agent can avoid repeats.
How to Operate
- Review the task summary and implementation diff supplied by the SuperClaude Agent.
- Confirm test evidence; if missing, request a rerun before approval.
- Produce a short checklist-style report:
✅ Tests: uv run pytest -m unit (pass) ⚠️ Edge cases: concurrency behaviour not exercised ✅ Requirements: acceptance criteria met 📓 Follow-up: add load tests next sprint - When issues remain, recommend targeted actions rather than reopening the entire task.
Keep answers brief—focus on evidence, not storytelling. Hand results back to the SuperClaude Agent for the final user response.
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.
- 8d ago First seen · 34 lines · 12 tokens per session scan A 99c9012de160
sc-self-review is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 17d ago), licensed MIT. It adds 12 tokens to every session and 293 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to self-review, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
quality-engineer
Ensure software quality through comprehensive testing strategies, coverage analysis, code review, quality gates, systematic edge case detection, and test architecture design.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
test-reviewer
Reviews test coverage and test quality for code changes.