performance

A coding assistant for finding where a program is slow or uses too many resources, then suggesting ways to improve it.

In plain words
What is it for?
Use it to investigate slow code, locate bottlenecks, review profiling results, and plan optimizations.
Why use it?
It helps identify performance problems that are difficult to spot by reading code alone.

Agent

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.

agentmods
npx agentmods add agents/miosa-osa/osa/performance
Clone the repo
git clone --depth 1 https://github.com/Miosa-osa/OSA
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 246 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00246
Opus 5 $0.00006 $0.00123
Sonnet 5 $0.00002 $0.00049
Haiku 4.5 $0.00001 $0.00025

Measured 2d ago against content hash 28fd83bedb4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

performance 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 2d 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.

priv/agents/performance.md · 37 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. 2d ago First seen · 37 lines · 12 tokens per session scan A 28fd83bedb4c

Subscribe to this mod's changes

performance is an agent published in the GitHub repository Miosa-osa/OSA (50 stars, last pushed 3d ago), with no licence file. It adds 12 tokens to every session and 246 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-08-30.

Related

Other agents, from other repositories

ApiExpert

Use when: designing C ABI APIs with opaque types and function pointer tables, creating header-only C++ wrappers over C APIs, adding new API surface area to the SDK, reviewing ABI stability, implementing vtable-based versioned interfaces, wrapping opaque handles with RAII C++ classes.

microsoft/foundry-local · 55 tokens

CppCoder

Use when: writing or modifying C++ implementation code, refactoring internal logic, implementing features behind the C ABI layer, writing tests, fixing bugs in .cc/.h files, optimizing performance, reviewing code for C++ Core Guidelines compliance, serializing/deserializing JSON, reducing code duplication.

microsoft/foundry-local · 58 tokens

Reviewer

Use when: reviewing C++ code for quality, checking memory safety and RAII compliance, verifying cross-platform portability, enforcing API consistency, reviewing for thread safety, checking const-correctness, auditing error handling patterns.

microsoft/foundry-local · 42 tokens

cicada-code-explorer

Fast code exploration and discovery. Use when you need to quickly find modules, functions, or understand code structure.

wende/cicada · 29 tokens

writer

You are a professional analyst and writer specializing in industry briefs. Your role is to synthesize research findings from multiple analysts into a polished, publication-ready brief.

jessedrelick/agens · 0 tokens

benchmark-advisor

Analyzes and compares MetriLLM benchmark results. Recommends the best local model for a given use case based on performance and quality scores.

MetriLLM/metrillm · 34 tokens