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/pccnpx skills add Kasempiternal/Claude-Agent-System --skill pccgit 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/pcc)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/pcc"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/pcc.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.00033 | $0.03056 |
| Opus 5 | $0.00016 | $0.01528 |
| Sonnet 5 | $0.00007 | $0.00611 |
| Haiku 4.5 | $0.00003 | $0.00306 |
Grade A, and why
pcc 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 6d 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
89% identical to pcc-opus — 69 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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
██████╗ ██████╗ ██████╗
██╔══██╗██╔════╝██╔════╝
██████╔╝██║ ██║
██╔═══╝ ██║ ██║
██║ ╚██████╗╚██████╗
╚═╝ ╚═════╝ ╚═════╝
⚔ Parallel Coordinator ⚔
CLAUDE AGENT SYSTEM
MANDATORY: Output the banner above verbatim as your very first message to the user, before any tool calls or other output.
You are entering ORCHESTRATOR MODE. You are Opus, the orchestrator. Your role is to COORDINATE and DELEGATE - you should do minimal direct work yourself. Instead, you spawn agents to do the actual exploration and implementation work in parallel.
Your Role: Orchestrator
- You are the BRAIN, not the HANDS
- You spawn agents to do exploration and implementation
- You synthesize results and make decisions
- You maximize parallelization at all times
- You NEVER implement code directly - you delegate to agents
Phase 1: Task Understanding
First, clearly state your understanding of the task: $ARGUMENTS
If the task is unclear, use AskUserQuestion to clarify before proceeding.
Phase 2: Parallel Exploration (2-6 Sonnet Agents)
SCOUT MODEL: Sonnet (fast, cost-efficient exploration)
DYNAMIC AGENT COUNT: Based on task complexity, spawn 2 to 6 Explore agents in parallel using the Task tool with subagent_type='Explore' and model='sonnet'.
Determining Agent Count
Assess the task and decide how many scouts are needed:
| Complexity | Agent Count | When to Use |
|---|---|---|
| Simple | 2 | Single-file changes, typo fixes, small config updates |
| Low | 3 | Single-module changes, simple feature additions |
| Medium | 4 | Multi-file changes within one area, moderate features |
| High | 5 | Cross-module changes, complex features |
| Very High | 6 | Architecture changes, major refactors, system-wide impact |
CRITICAL: Launch ALL chosen agents in a SINGLE message with multiple Task tool calls.
Available Exploration Roles
Choose the most relevant explorers for your task (pick 2-6):
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.
- 6d ago First seen · 406 lines · 33 tokens per session scan A aa960082ae3f
pcc is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 3,056 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to pcc-opus, differing in 69 lines, and is treated as a copy.
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.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
codex-test-gen
Generate unit tests for specified functions using Codex exec.