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/commands/superclaude-org/superclaude_plugin/sc-implement)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-implement"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-implement/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-implement"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-implement.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00980 |
| Opus 5.5 | $0.00005 | $0.00392 |
| Sonnet 5.5 | $0.00003 | $0.00196 |
| Haiku 4.5 | $0.00001 | $0.00098 |
Grade A, and why
implement 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 1mo 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
86% identical to implement — 28 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:implement - Feature Implementation
Context Framework Note: This behavioral instruction activates when Claude Code users type
/sc:sc:implementpatterns. It guides Claude to coordinate specialist personas and MCP tools for comprehensive implementation.
Triggers
- Feature development requests for components, APIs, or complete functionality
- Code implementation needs with framework-specific requirements
- Multi-domain development requiring coordinated expertise
- Implementation projects requiring testing and validation integration
Context Trigger Pattern
/sc:sc:implement [feature-description] [--type component|api|service|feature] [--framework react|vue|express] [--safe] [--with-tests]
Usage: Type this in Claude Code conversation to activate implementation behavioral mode with coordinated expertise and systematic development approach.
Behavioral Flow
- Analyze: Examine implementation requirements and detect technology context
- Plan: Choose approach and activate relevant personas for domain expertise
- Generate: Create implementation code with framework-specific best practices
- Validate: Apply security and quality validation throughout development
- Integrate: Update documentation and provide testing recommendations
Key behaviors:
- Context-based persona activation (architect, frontend, backend, security, qa)
- Framework-specific implementation via Context7 and Magic MCP integration
- Systematic multi-component coordination via Sequential MCP
- Comprehensive testing integration with Playwright for validation
MCP Integration
- Context7 MCP: Framework patterns and official documentation for React, Vue, Angular, Express
- Magic MCP: Auto-activated for UI component generation and design system integration
- Sequential MCP: Complex multi-step analysis and implementation planning
- Playwright MCP: Testing validation and quality assurance integration
- Availability fallback: The MCP servers named here are preferred tooling, not hard requirements — when one is not installed, degrade gracefully (native reasoning in place of Sequential, official docs via web lookup in place of Context7, native tools otherwise) instead of routing work to absent servers.
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.
- 1mo ago Changed · +2 lines a67d4275563e
- 1mo ago First seen · 111 lines · 13 tokens per session scan A 4797888d4d11
implement is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 20d ago), licensed MIT. It adds 13 tokens to every session and 980 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to implement, differing in 28 lines, and is treated as a copy.
Other commands, from other repositories
spec-research
A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.
triage
Triage Linear issue with comprehensive analysis.
land
Resolve and squash merge one named, currently authorized pull request.
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
slack-gif-creator
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.