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 skills add inbharatai/claude-skills --skill perf-optimizergit clone --depth 1 https://github.com/inbharatai/claude-skillsWrote 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/inbharatai/claude-skills/perf-optimizer)<a href="https://agentmods.dev/skills/inbharatai/claude-skills/perf-optimizer"><img src="https://agentmods.dev/badge/skills/inbharatai/claude-skills/perf-optimizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/inbharatai/claude-skills/perf-optimizer"><img src="https://agentmods.dev/badge/skills/inbharatai/claude-skills/perf-optimizer.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00394 |
| Opus 5 | $0.00012 | $0.00197 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
perf-optimizer 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 7d 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.
What it actually says
Performance Optimizer
Overview
Profile and optimize application performance — algorithmic complexity, caching strategies, database queries, and bundle size.
When to Use This Skill
Use Performance Optimizer when you need to:
- Work with performance optimizer tasks in your project or workflow
- Automate performance optimizer operations at scale
- Generate production-quality performance optimizer output quickly
Instructions
When this skill is active, Claude will:
- Understand the full context of your performance optimizer request
- Apply best practices and conventions for Development
- Produce clean, well-structured, production-ready output
- Explain key decisions and offer alternatives where relevant
Examples
Example 1 — Basic Usage
User: Help me get started with performance optimizer.
Claude: I'll walk you through the essential steps for performance optimizer in your context...
Example 2 — Advanced Usage
User: I need a production-ready performance optimizer setup with full error handling.
Claude: Here's a complete, production-hardened performance optimizer implementation...
Guidelines
- Always validate inputs before processing
- Follow the conventions of the target platform or language
- Prefer explicit over implicit — clarity beats cleverness
- Include comments for non-obvious logic
- Suggest tests or validation steps where appropriate
Dependencies
Required: none
Platforms
Available on: claude.ai, claude-code, api
Part of the claude-skills collection — 183+ skills for Claude.
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.
- 7d ago First seen · 68 lines · 24 tokens per session scan A 2d09a5f47f53
perf-optimizer is a skill published in the GitHub repository inbharatai/claude-skills (33 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 394 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-09-03.
Other skills, from other repositories
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…
log-analyzer
Senior-SRE log analysis specialist. Use when investigating incidents from logs, triaging error spikes, extracting timelines, correlating distributed traces, or separating signal from noise across plain-text, JSON (slog/zap), syslog, journald, container, and Kubernetes logs. ALWAYS use when the user asks to "analyze…
incident-postmortem
Incident post-mortem specialist for writing blameless post-mortems, extracting timelines from logs/events, conducting root cause analysis (5-Why, fishbone), classifying severity, and generating tracked action items. ALWAYS use when writing a post-mortem, reviewing an incident, extracting a timeline, performing root…
systematic-debugging
Use when debugging, diagnosing, or investigating any bug, test failure, flaky test, race condition, unexpected behavior, build failure, production incident, third-party breakage, root cause analysis, or performance regression before proposing fixes.
thirdparty-api-integration-test
Create and run gated Go integration tests for third-party APIs with real external calls, strict configuration gates, bounded timeouts, and safe runtime controls. Use for vendor/client contract verification and failure triage.