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 skills/kasempiternal/claude-agent-system/systemccnpx skills add Kasempiternal/Claude-Agent-System --skill systemccgit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/skills/kasempiternal/claude-agent-system/systemcc)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/systemcc"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/systemcc.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.00039 | $0.03915 |
| Opus 5 | $0.00019 | $0.01958 |
| Sonnet 5 | $0.00008 | $0.00783 |
| Haiku 4.5 | $0.00004 | $0.00392 |
Grade A, and why
systemcc 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.
How it starts
The opening of the file, as written. The whole thing — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
███████╗██╗ ██╗███████╗████████╗███████╗███╗ ███╗
██╔════╝╚██╗ ██╔╝██╔════╝╚══██╔══╝██╔════╝████╗ ████║
███████╗ ╚████╔╝ ███████╗ ██║ █████╗ ██╔████╔██║
╚════██║ ╚██╔╝ ╚════██║ ██║ ██╔══╝ ██║╚██╔╝██║
███████║ ██║ ███████║ ██║ ███████╗██║ ╚═╝ ██║
╚══════╝ ╚═╝ ╚══════╝ ╚═╝ ╚══════╝╚═╝ ╚═╝
⚔ Command Center ⚔
CLAUDE AGENT SYSTEM
MANDATORY: Output the banner above verbatim as your very first message to the user, before any tool calls or other output.
SystemCC - Master Command Router
User types: /systemcc "any task"
Claude does: EVERYTHING automatically
Phase 1: CRITICAL DETECTION (MANDATORY)
When /systemcc is detected, you MUST IMMEDIATELY show:
🎯 SYSTEMCC DETECTED - Command acknowledged and workflow initiated
✅ Following SYSTEMCC workflow instructions
This message MUST appear:
- IMMEDIATELY when /systemcc is detected
- BEFORE any other processing
- CANNOT BE SKIPPED under any circumstances
Phase 2: LYRA AI PROMPT OPTIMIZATION (MANDATORY)
After detection, ALWAYS show Lyra optimization with this EXACT format:
═══════════════════════════════════════════════════════════════
🎯 LYRA AI PROMPT OPTIMIZATION
═══════════════════════════════════════════════════════════════
📝 Original Request:
"$ARGUMENTS"
🔍 Analysis Phase:
- Deconstructing intent...
- Diagnosing gaps...
- Developing enhancements...
- Delivering optimized prompt...
✨ Optimized Prompt:
"[enhanced prompt with complete specifications]"
📊 Optimization Details:
- Mode: [BASIC/DETAIL]
- Complexity Score: [1-10]
- Improvements Applied: [number]
🔧 Key Enhancements:
• [Enhancement 1]
• [Enhancement 2]
• [Enhancement 3]
═══════════════════════════════════════════════════════════════
The 4-D Methodology
- DECONSTRUCT: Extract coding intent, feature requirements, technical context
- DIAGNOSE: Audit for technical clarity and specification gaps
- DEVELOP: Select optimal techniques based on request type:
- Bug Fixes → Precise error context + systematic debugging
- Feature Development → Clear requirements + implementation scope
- Refactoring → Architecture goals + code quality standards
- UI/UX → Design principles + user experience objectives
- DELIVER: Construct development-focused prompt with complete specs
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 · 539 lines · 39 tokens per session scan A 4da41311dcc2
systemcc is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 3,915 once invoked, about $0.0002 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 skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…