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 autohandai/code-cli --skill performance-analysisgit clone --depth 1 https://github.com/autohandai/code-cliWrote 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/autohandai/code-cli/performance-analysis)<a href="https://agentmods.dev/skills/autohandai/code-cli/performance-analysis"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/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.
<a href="https://agentmods.dev/skills/autohandai/code-cli/performance-analysis"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/performance-analysis.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.00059 | $0.00491 |
| Opus 5.5 | $0.00024 | $0.00196 |
| Sonnet 5.5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
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.
What it actually says
Analyze performance with numbers
Optimizing without a measurement changes the code without changing the outcome. Every step below produces a number you can show.
Establish the baseline
- Define the metric and the scenario exactly: what is slow, from which event to which, on what input size, on what machine. Ask if unclear.
- Measure it three times with the tools the project already has (timers,
--profileflags,time,hyperfine, language profilers,--cpu-prof, heap snapshots, bundle analyzers). Record median and spread. - Record the environment: load average, CPU count, disk free, network, concurrent processes. A loaded machine invalidates comparisons.
Find the dominant cost
- Break the total into phases with timestamps or a profiler; sort by time.
- Distinguish blocking waits (network, disk, subprocess, locks, timeouts) from CPU work; the fix differs.
- Look for the usual shapes: sequential awaits that could be parallel, work repeated per item that could be cached, unbounded scans that need a budget, startup work that could be lazy or deferred, N+1 calls, large payloads, synchronous I/O on the main thread, retries with long timeouts.
- Check what scales with input size using two sizes and compare.
Change one thing, then measure again
- Pick the change with the best ratio of expected gain to risk. State the expected gain before making it.
- Re-measure the same way. Report before and after with the spread.
- Add a guard so it stays fixed: a timing assertion with a generous bound, a budget constant, or a test that the work is deferred or cached.
Report
Metric, scenario, baseline, cause with file:line, change, result, and what was not addressed. If the measurement showed the suspected cause was wrong, say so.
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.
- 1mo ago First seen · 45 lines · 59 tokens per session scan A b5e227d6fed7
performance-analysis is a skill published in the GitHub repository autohandai/code-cli (205 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 491 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-09-15.
Other skills, from other repositories
neuron-monitoring
Monitor Neuron AI agents and workflows with events observability, logging, and performance analysis. Use this skill whenever the user mentions debugging, monitoring, observability, performance analysis, tracing, or needs to understand why an agent is behaving a certain way. Also trigger for tasks involving agent…
evidence-audit
Evidence-led audit/fix rounds for any codebase in any language. Finds only defects that a runnable proof reproduces on current code, applies the narrowest in-scope patch, verifies with a second proof, promotes high-risk proofs to permanent regression tests, and reports exact validation results. Use whenever the user…
bug-hunter
Use this skill when scanning source code for bugs, anti-patterns, code smells, or quality issues in a codebase, or when running a proof-driven bug hunt that must find, prove, fix, and verify one real defect. Trigger on the explicit vocabulary — "bug", "bug hunt", "/bughunt", "scan for issues", "find problems"…
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
observability
Use this skill when adding or reviewing logging, metrics, or tracing in an application, or when a production problem can't be diagnosed from the signals that exist today. Triggers: user says "logging", "logs", "trace", "tracing", "metrics", "observability", "instrument", "OpenTelemetry", "structured logging", "log…
remote-debugging
Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence. Use when local behavior differs from a known server or deployment; start read-only and keep diagnosis separate from disruptive remediation.