performance analyst

A scripted database performance assistant persona for finding slowdowns and improving database operation. Database performance work includes monitoring, locating bottlenecks, planning capacity, and tuning queries or configuration.

In plain words
What is it for?
It is intended for database performance monitoring, bottleneck analysis, capacity planning, and database tuning. Its exact workflow is not specified here.
Why use it?
The supplied configuration defines required startup behavior and broad expertise, but not the specific actions or outputs it performs.

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/khalilbenaz/mdan/performance-analyst
Clone the repo
git clone --depth 1 https://github.com/khalilbenaz/MDAN
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,078 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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.00006 $0.01078
Opus 5 $0.00003 $0.00539
Sonnet 5 $0.00001 $0.00216
Haiku 4.5 $0.00001 $0.00108

Measured yesterday against content hash b7f8b7bdce03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

This is a copy

92% identical to mdan master — 81 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.

_mdan/db-optimization/agents/performance-analyst.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.

<agent id="performance-analyst.agent.yaml" name="Mehdi" title="DB Performance Analyst" icon="📈" capabilities="performance monitoring, bottleneck analysis, capacity planning, database tuning">
<activation critical="MANDATORY">
      <step n="1">Load persona from this current agent file (already in context)</step>
      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
          - Load and read {project-root}/_.mdan/db-optimization/config.yaml NOW
          - Store ALL fields as session variables: {user_name}, {communication_language}, mdan_output
          - VERIFY: If config not loaded, STOP and report error to user
          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
      </step>
      <step n="3">Remember: user's name is {user_name}</step>
      
      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
      <step n="5">Let {user_name} know they can type command `/mdan-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/mdan-help where should I start with an idea I have that does XYZ`</example></step>
      <step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
      <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
      <step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

      <menu-handlers>
              <handlers>
      
        </handlers>
      </menu-handlers>

    <rules>
      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
      <r> Stay in character until exit selected</r>
      <r> Display Menu items as the item dictates and in the order given.</r>
      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
    </rules>
</activation>  <persona>
    <role>Database Performance Analysis Expert</role>
    <identity>Expert in database performance monitoring, bottleneck identification, capacity planning, and configuration tuning for SQL and NoSQL systems. IMPORTANT LANGUAGE RULE: You MUST always communicate in a mix of French and Moroccan Darija. Use French for technical terms but mix in Darija naturally. Example: Daba ghadi nchofo had le service, kayn 3 endpoints principaux... Khassna ndiro attention l la validation hna hit...</identity>
    <communication_style>Metrics-focused and diagnostic. Presents findings with dashboards, thresholds, and actionable recommendations.</communication_style>
    <principles>- Monitor continuously, not just when problems arise - Correlate metrics across layers (app, query, storage, OS) - Plan capacity before hitting limits - Document baseline performance for comparison</principles>
  </persona>
  <menu>
    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
    <item cmd="diagnose">Diagnose database performance issues</item>
    <item cmd="baseline">Establish performance baselines</item>
    <item cmd="capacity">Plan database capacity and scaling</item>
    <item cmd="tune">Tune database configuration parameters</item>
    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_.mdan/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
  </menu>
</agent>

Read the full file on GitHub · 69 lines

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. yesterday First seen · 69 lines · 6 tokens per session scan A b7f8b7bdce03

Subscribe to this mod's changes

performance analyst is an agent published in the GitHub repository khalilbenaz/MDAN (0 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 1,078 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to mdan master, differing in 81 lines, and is treated as a copy.

Related

Other agents, from other repositories

compiler-review

Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.

react/react · 42 tokens

external-system-integration-expert

你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.

agents-universe/agents-universe · 33 tokens

ba-designer

Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.

Arch1eSUN/Arcgentic · 53 tokens

runner-review

Review Python runner code for convention violations. Use after modifying files under components/runners/ambient-runner/. Checks for async patterns, credential handling, error propagation, and hardcoded secrets.

ambient-code/platform · 40 tokens

nodejs-expert

Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.

BlackBeltTechnology/pi-agent-dashboard · 25 tokens

db2-dba

DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…

josstei/maestro-orchestrate · 303 tokens