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_framework/implementgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWhat 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.00013 | $0.00808 |
| Opus 5 | $0.00006 | $0.00404 |
| Sonnet 5 | $0.00003 | $0.00162 |
| Haiku 4.5 | $0.00001 | $0.00081 |
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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- implement — 86% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:implement - Feature Implementation
Context Framework Note: This behavioral instruction activates when Claude Code users type
/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: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
Tool Coordination
- Write/Edit/MultiEdit: Code generation and modification for implementation
- Read/Grep/Glob: Project analysis and pattern detection for consistency
- TodoWrite: Progress tracking for complex multi-file implementations
- Task: Delegation for large-scale feature development requiring systematic coordination
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.
- yesterday First seen · 97 lines · 13 tokens per session scan A 91bc8be54c6a
implement is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,852 stars, last pushed 11d ago), licensed MIT. It adds 13 tokens to every session and 808 once invoked, about $0.0001 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-30.
Other commands, from other repositories
pr-address
Address PR review comments on current branch.
plan-save
Save the current session's plan to GitHub as an issue.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
OPSX: Verify
Verify implementation matches change artifacts before archiving.