perf-code-paths

perf-code-paths is a skill for Claude Code, Kiro from Najeebullah3124/awesome-claude-universe. It costs 21 tokens per session (193 once invoked), scanned A, original, no licence file.

A tool for mapping code paths, entry points, and files that may be performance hot spots before profiling.

In plain words
What is it for?
Use it to trace how execution enters and moves through the code before measuring runtime behavior.
Why use it?
It narrows the investigation to the parts of a codebase most likely to affect performance.

Skill for Claude CodeKiro

Written for Claude Code and Kiro: shipped in a Claude Code plugin, but also installed under .kiro/.

Part of the agentsys plugin — 30 skills shipped together

Good fit Use it to trace how execution enters and moves through the code before measuring runtime behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/najeebullah3124/awesome-claude-universe/perf-code-paths
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 Najeebullah3124/awesome-claude-universe --skill perf-code-paths
Clone the repo
git clone --depth 1 https://github.com/Najeebullah3124/awesome-claude-universe

Made for: Claude Code, Kiro.

Or install agentsys, the plugin that ships this one along with the rest of its 30 skills.

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 perf-code-paths

README.md
[![agentmods](https://agentmods.dev/badge/skills/najeebullah3124/awesome-claude-universe/perf-code-paths/github.svg)](https://agentmods.dev/skills/najeebullah3124/awesome-claude-universe/perf-code-paths)
Your own site
<a href="https://agentmods.dev/skills/najeebullah3124/awesome-claude-universe/perf-code-paths"><img src="https://agentmods.dev/badge/skills/najeebullah3124/awesome-claude-universe/perf-code-paths/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 perf-code-paths

Your own site · 80×15
<a href="https://agentmods.dev/skills/najeebullah3124/awesome-claude-universe/perf-code-paths"><img src="https://agentmods.dev/badge/skills/najeebullah3124/awesome-claude-universe/perf-code-paths.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 193 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.
Origin unknown 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.00021 $0.00193
Opus 5 $0.00010 $0.00097
Sonnet 5 $0.00004 $0.00039
Haiku 4.5 $0.00002 $0.00019

Measured 8d ago against content hash f81bc21cf4b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

perf-code-paths 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 8d 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.

agentsys/.kiro/skills/perf-code-paths/SKILL.md · 33 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 8d ago First seen · 33 lines · 21 tokens per session scan A f81bc21cf4b0

Subscribe to this mod's changes

perf-code-paths is a skill published in the GitHub repository Najeebullah3124/awesome-claude-universe (2 stars, last pushed 1mo ago), with no licence file. It adds 21 tokens to every session and 193 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.

Related

Other skills, from other repositories

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

affaan-m/ECC · 46 tokens

eslint-fix

A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.

laolaoshiren/claude-code-skills-zh · 79 tokens

manage-skills

A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.

sangrokjung/claude-forge · 54 tokens

systematic-debugging

Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.

sangrokjung/claude-forge · 53 tokens

review-loop

Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…

sangrokjung/claude-forge · 100 tokens

semgrep-rule-creator

Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.

waybarrios/opencode-power-pack · 37 tokens