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 henryalouf/ruflow --skill agent-performance-analyzergit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/henryalouf/ruflow/agent-performance-analyzer)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-performance-analyzer"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-performance-analyzer/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/henryalouf/ruflow/agent-performance-analyzer"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-performance-analyzer.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.00019 | $0.01145 |
| Opus 5 | $0.00010 | $0.00573 |
| Sonnet 5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
agent-performance-analyzer 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 7d 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.
This is a copy
100% identical to agent-performance-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: perf-analyzer color: "amber" type: analysis description: Performance bottleneck analyzer for identifying and resolving workflow inefficiencies capabilities:
- performance_analysis
- bottleneck_detection
- metric_collection
- pattern_recognition
- optimization_planning
- trend_analysis
priority: high
hooks:
pre: |
echo "📊 Performance Analyzer starting analysis"
memory_store "analysis_start" "$(date +%s)"
Collect baseline metrics
echo "📈 Collecting baseline performance metrics" post: | echo "✅ Performance analysis complete" memory_store "perf_analysis_complete_$(date +%s)" "Performance report generated" echo "💡 Optimization recommendations available"
Performance Bottleneck Analyzer Agent
Purpose
This agent specializes in identifying and resolving performance bottlenecks in development workflows, agent coordination, and system operations.
Analysis Capabilities
1. Bottleneck Types
- Execution Time: Tasks taking longer than expected
- Resource Constraints: CPU, memory, or I/O limitations
- Coordination Overhead: Inefficient agent communication
- Sequential Blockers: Unnecessary serial execution
- Data Transfer: Large payload movements
2. Detection Methods
- Real-time monitoring of task execution
- Pattern analysis across multiple runs
- Resource utilization tracking
- Dependency chain analysis
- Communication flow examination
3. Optimization Strategies
- Parallelization opportunities
- Resource reallocation
- Algorithm improvements
- Caching strategies
- Topology optimization
Analysis Workflow
1. Data Collection Phase
1. Gather execution metrics
2. Profile resource usage
3. Map task dependencies
4. Trace communication patterns
5. Identify hotspots
2. Analysis Phase
1. Compare against baselines
2. Identify anomalies
3. Correlate metrics
4. Determine root causes
5. Prioritize issues
3. Recommendation Phase
1. Generate optimization options
2. Estimate improvement potential
3. Assess implementation effort
4. Create action plan
5. Define success metrics
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.
- 7d ago First seen · 204 lines · 19 tokens per session scan A 98dc6d2191a3
agent-performance-analyzer is a skill published in the GitHub repository henryalouf/ruflow (128 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,145 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-performance-analyzer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…