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 agentmods add skills/cofin/flow/performance-analystnpx skills add cofin/flow --skill performance-analystgit clone --depth 1 https://github.com/cofin/flowWhat 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 | $0.00043 | $0.00327 |
| Opus 5 | $0.00022 | $0.00163 |
| Sonnet 5 | $0.00009 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
performance-analyst 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.
What it actually says
Performance Analyst
Review measured hot paths for bottlenecks, scaling concerns, and resource waste. Use directly or as a performance-focused review subagent.
Workflow
- Load the performance persona and checklist below.
- Establish the actual hot path and available measurements.
- Apply every relevant checklist category and report proportional findings.
Guardrails
Follow the persona boundaries. Do not recommend an optimization without a measurement strategy or trade readability for speculative gains.
Output
For each finding, state the bottleneck, the metric that proves it, expected impact as critical/moderate/minor, and the recommended change. Explain briefly when the path is already efficient.
Validation
Confirm every recommendation targets a real hot path and includes a way to measure its effect.
Example
Report an N+1 request path with its observed query count, expected latency impact, and the before/after measurement needed for the proposed batching fix.
References
- Persona — performance role, measurement principle, and boundaries.
- Performance checklist — hot-path and resource checks.
- Stances — optional tradeoff views.
What ships with it
3 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.
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.
- 2d ago First seen · 59 lines · 43 tokens per session scan A 74e6563468d1
performance-analyst is a skill published in the GitHub repository cofin/flow (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 43 tokens to every session and 327 once invoked, about $0.0002 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.
Other skills, from other repositories
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.