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/evan043/claude-cli-advanced-starter-pack/perf-profile.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/perf-profile.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/perf-profile.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/perf-profile.template.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.00000 | $0.02705 |
| Opus 5 | $0.00000 | $0.01352 |
| Sonnet 5 | $0.00000 | $0.00541 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
perf-profile.template 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.
How it starts
The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Performance profiling and optimization analysis type: project complexity: medium allowed-tools: Bash, Read, Grep, Glob category: performance
/perf-profile
Analyze application performance and identify optimization opportunities.
Usage
/perf-profile
/perf-profile --web
/perf-profile --bundle
/perf-profile --runtime
What It Does
- Web Performance - Lighthouse audit for web apps
- Bundle Analysis - Identify large dependencies
- Core Web Vitals - Check LCP, FID, CLS
- Memory Profiling - Memory leak detection
- Import Cost - Analyze dependency sizes
Step 1: Lighthouse Audit (Web Projects)
{{#if frontend.framework}}
Run Lighthouse on your application:
# Install Lighthouse CLI
npm install -g lighthouse
# Run audit (dev server must be running)
lighthouse http://localhost:{{frontend.devServerPort || 5173}} \
--output=json \
--output-path=./lighthouse-report.json \
--only-categories=performance,accessibility,best-practices
# Parse results
cat lighthouse-report.json | jq '.categories.performance.score * 100'
Key Metrics
- Performance Score: Target 90+
- First Contentful Paint (FCP): Target < 1.8s
- Largest Contentful Paint (LCP): Target < 2.5s
- Total Blocking Time (TBT): Target < 200ms
- Cumulative Layout Shift (CLS): Target < 0.1
- Speed Index: Target < 3.4s
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 · 474 lines · 0 tokens per session scan A a1b81d393025
perf-profile.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,705 tokens. 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
verify-loop
자동 재검증 루프 (최대 3회 재시도, 실패 시 자동 수정).
build-fix
빌드 에러를 자동으로 분석하고 수정합니다.
gates-csk
Gate report — what the tool-level gates actually did, and which rules nothing has tripped.
health-check
Run diagnostics on Claude Code toolkit configuration and status.
assert
Validate implementation completeness, correctness, and compliance before testing phase through static analysis and requirements verification.
bootstrap
Verifies and repairs the Claude Code Toolkit installation.