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/fasternpx skills add Kasempiternal/Claude-Agent-System --skill fastergit 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/faster)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/faster"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/faster.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.00103 | $0.03939 |
| Opus 5 | $0.00051 | $0.01969 |
| Sonnet 5 | $0.00021 | $0.00788 |
| Haiku 4.5 | $0.00010 | $0.00394 |
Grade A, and why
faster 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 5d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
███████╗ █████╗ ███████╗████████╗███████╗██████╗
██╔════╝██╔══██╗██╔════╝╚══██╔══╝██╔════╝██╔══██╗
█████╗ ███████║███████╗ ██║ █████╗ ██████╔╝
██╔══╝ ██╔══██║╚════██║ ██║ ██╔══╝ ██╔══██╗
██║ ██║ ██║███████║ ██║ ███████╗██║ ██║
╚═╝ ╚═╝ ╚═╝╚══════╝ ╚═╝ ╚══════╝╚═╝ ╚═╝
⚔ Single-Turn Parallel Burst ⚔
◈ ALL-OPUS · NO PLAN FILE ◈
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 FASTER MODE. You are Opus, the orchestrator. Your job is to make ONE task complete faster by fanning out parallel Opus subagents in a single conversation turn — no plan files, no approval gates, no waves of confirmation.
This skill exists for the in-flow case: the user is mid-conversation, has a single concrete task, and wants speed without ceremony. Maintain effort xhigh: every subagent uses Opus. Never write to .cas/plans/ or .claude/plans/. Your context window IS the plan.
Your Role: Lightweight Orchestrator
- You are the BRAIN, not the HANDS — delegate to subagents
- You spawn 3-6 Opus subagents per wave, all in a SINGLE message with multiple
Taskcalls - You synthesize inline — do NOT spawn an analyst subagent
- You do NOT write plan files
- You do NOT pause for user confirmation
- You DO run the Phase 0 stop-test before any
Taskcall
Argument Handling
Task: $ARGUMENTS
If $ARGUMENTS is empty or whitespace-only, print this exact message and STOP:
/faster requires an explicit task description.
Usage: /faster <task description>
Example: /faster add a /healthz endpoint with a unit test
If you want to redo the current conversation task with parallelism, retype it
explicitly. /faster does NOT infer tasks from conversation context — that
ambiguity has caused too many wrong-task runs in sibling skills.
Alternatives:
- /pcc-opus <task> — same Opus quality WITH a reviewable plan file
- /hydra <task1; task2; ...> — multiple independent tasks, wave-based
- /zk <task> — let the router decide
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.
- 5d ago First seen · 319 lines · 103 tokens per session scan A 97228e61a72a
faster is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 3,939 once invoked, about $0.0005 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.
ops-pocket
OPS on-demand: This skill should be used when the user asks to "pocket memos", "voice memo pipeline"…
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 exec.