performance-analysis

performance-analysis is a skill for Claude Code from rsmdt/the-startup. It costs 42 tokens per session (942 once invoked), scanned A, original, MIT.

A performance investigation guide for finding where software is slow or uses too many resources. It uses measurements and profiling before suggesting changes.

In plain words
What is it for?
Use it to establish performance baselines, investigate CPU, memory, input/output, locking, or database-query problems, and plan for growth.
Why use it?
It helps avoid guessing at optimizations that do not address the real bottleneck. It also provides a consistent way to compare performance before and after changes.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the team plugin — 16 skills, 2 agents shipped together

Good fit Use it to establish performance baselines, investigate CPU, memory, input/output, locking, or database-query problems, and plan for growth.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rsmdt/the-startup/performance-analysis
Install

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.

Any agent
npx skills add rsmdt/the-startup --skill performance-analysis
Clone the repo
git clone --depth 1 https://github.com/rsmdt/the-startup

Made for: Claude Code.

Or install team, the plugin that ships this one along with the rest of its 16 skills, 2 agents.

Wrote 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.

agentmods badge for performance-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/rsmdt/the-startup/performance-analysis/github.svg)](https://agentmods.dev/skills/rsmdt/the-startup/performance-analysis)
Your own site
<a href="https://agentmods.dev/skills/rsmdt/the-startup/performance-analysis"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/performance-analysis/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.

agentmods 80×15 button for performance-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/rsmdt/the-startup/performance-analysis"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/performance-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 942 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.00942
Opus 5.5 $0.00017 $0.00377
Sonnet 5.5 $0.00008 $0.00188
Haiku 4.5 $0.00004 $0.00094

Measured 1mo ago against content hash e378597e2c0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

performance-analysis 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 1mo 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.

plugins/team/skills/quality/performance-analysis/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Persona

Act as a performance engineer who applies systematic measurement and profiling to identify actual bottlenecks before recommending targeted optimizations. Follow the golden rule: measure first, optimize second.

Analysis Target: $ARGUMENTS

Interface

BottleneckFinding { category: CPU | Memory | IO | Lock | Query severity: CRITICAL | HIGH | MEDIUM | LOW component: string symptom: string evidence: string // measurement data supporting the finding impact: string recommendation: string }

ProfilingLevel { level: Application | System | Infrastructure metrics: string[] }

State { target = $ARGUMENTS profilingLevels = [ Application, System, Infrastructure ] metrics = {} bottlenecks: BottleneckFinding[] baseline = {} }

Constraints

Always:

  • Establish baseline metrics before any optimization recommendation.
  • Every recommendation must cite measurement evidence.
  • Use percentiles (p50, p95, p99) for latency — never averages alone.
  • Profile at the right level to find the actual bottleneck.
  • Apply Amdahl's Law: focus on biggest contributors first.

Never:

  • Recommend optimization without measurement evidence.
  • Profile only in development — production-like environments required.
  • Ignore tail latencies (p99, p999).
  • Optimize non-bottleneck code prematurely.
  • Cache without defining an invalidation strategy.

Reference Materials

  • reference/profiling-tools.md — Tools by language and platform (Node.js, Python, Java, Go, browser, database, system)
  • reference/optimization-patterns.md — Quick wins, algorithmic improvements, architectural changes, capacity planning

Workflow

1. Gather Context

Understand the performance concern: what symptom is observed? Establish baseline metrics before any changes.

Core methodology — follow this order:

  1. Measure — establish baseline metrics
  2. Identify — find the actual bottleneck
  3. Hypothesize — form a theory about the cause
  4. Fix — implement targeted optimization
  5. Validate — measure again to confirm improvement
  6. Document — record findings and decisions

Read the full file on GitHub · 135 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago First seen · 135 lines · 42 tokens per session scan A e378597e2c0d

Subscribe to this mod's changes

performance-analysis is a skill published in the GitHub repository rsmdt/the-startup (568 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 942 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

operating-cadence

Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…

cbrock84/headcount · 95 tokens

broken-links

Find and fix broken links — three modes with different scale ceilings. local audits any local repo (HTML/MD/MDX, no size limit) via Glob/Grep + per-link verification. page checks one live URL deeply (30-100 outbound links per run). site requires the Ahrefs site-audit MCP for true multi-page crawl — without it, refuses…

akii-technologies-ltd/akii-seo-ai-search-optimizer · 162 tokens

audit-project

Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".

OutlineDriven/odin-claude-plugin · 50 tokens

sofa-search

Search Stack Overflow for Agents (SOFA) for a peer-verified solution before solving from scratch. TRIGGER when: about to debug an unfamiliar error, integrate a new API/library, or research an unfamiliar pattern, and SOFA is configured. SKIP: root-causing a bug in your own code (use systematic-debugging); SOFA…

komluk/scaffolding · 79 tokens

error-handling

Consistent error handling across frontend and backend layers. TRIGGER when: implementing error boundaries, exception handlers, or try/catch blocks. SKIP: shaping HTTP error response bodies (use api-design); logging the error (use logging-standards). (Examples in React + Python.).

komluk/scaffolding · 61 tokens

optimize

Use when asked to optimize code, make a path faster, make this as fast as possible, reduce allocations, repair a regression, profile a target, grill every inefficiency, or run a subsystem or repo-wide performance campaign against a measured floor; when a performance requirement, slowness report, Core Web Vitals miss…

OutlineDriven/odin-claude-plugin · 123 tokens