n98-magerun2-performance-review: Agent for Claude Code

.claude/agents/analyzer-creator.md

analyzer-creator is an agent for Claude Code from magendooro/n98-magerun2-performance-review. It costs 64 tokens per session (3,757 once invoked), scanned A, original, MIT.

A specialised helper for creating custom performance checks for Magento, an e-commerce platform. It first gathers requirements and then produces an analyzer with error handling, documentation, and testing guidance.

In plain words
What is it for?
Use it to monitor Magento configuration, database tables, files, resources, or custom module behaviour, and to add a new analyzer to the Performance Review module.
Why use it?
It gives performance-monitoring work a defined process and helps fit new checks into the existing module. It also distinguishes creating a check from debugging or optimising one that already exists.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is magendooro/n98-magerun2-performance-review's own configuration. It tells Claude Code how to work on n98-magerun2-performance-review itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything n98-magerun2-performance-review configures →

Reuse

Borrowing it

Nothing to install: this file belongs to magendooro/n98-magerun2-performance-review. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/magendooro/n98-magerun2-performance-review/main/.claude/agents/analyzer-creator.md
Clone the repo
git clone --depth 1 https://github.com/magendooro/n98-magerun2-performance-review

Made for: Claude Code.

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

agentmods badge for analyzer-creator

README.md
[![agentmods](https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/analyzer-creator/github.svg)](https://agentmods.dev/agents/magendooro/n98-magerun2-performance-review/analyzer-creator)
Your own site
<a href="https://agentmods.dev/agents/magendooro/n98-magerun2-performance-review/analyzer-creator"><img src="https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/analyzer-creator/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.

agentmods 80×15 button for analyzer-creator

Your own site · 80×15
<a href="https://agentmods.dev/agents/magendooro/n98-magerun2-performance-review/analyzer-creator"><img src="https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/analyzer-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,757 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00064 $0.03757
Opus 5 $0.00032 $0.01878
Sonnet 5 $0.00013 $0.00751
Haiku 4.5 $0.00006 $0.00376

Measured 11d ago against content hash e3e1b39a0ef2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

analyzer-creator 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 11d 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.

.claude/agents/analyzer-creator.md · 532 lines

How it starts

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

Analyzer Creator Agent

You are a specialized agent for creating custom analyzers for the n98-magerun2 Performance Review module.

Your Mission

Create complete, working, production-ready custom analyzers from user requirements. Deliver code that works on first run with proper error handling, clear documentation, and testing guidance.

When To Use This Agent

Use when user asks to:

  • Create a new analyzer or performance check
  • Add monitoring for specific Magento aspects
  • Check custom configuration or setup
  • Monitor database tables, files, or resources
  • Validate custom module behavior

Do NOT use when:

  • User wants to modify existing core analyzers (suggest using code editor directly)
  • User wants to debug non-working analyzer (use analyzer-debugger instead)
  • User wants to optimize slow analyzer (use performance-optimizer instead)

Your Workflow

Phase 1: Requirements Gathering (Always Start Here)

Before writing any code, gather complete requirements by reading CLAUDE.md and asking clarifying questions:

  1. Read CLAUDE.md first to understand patterns and available dependencies

  2. Ask user:

    • What specific aspect of Magento should be analyzed?
    • What indicates a problem (specific threshold, condition, or state)?
    • What priority should issues have (high/medium/low) and why?
    • Where should the analyzer look (database, files, configuration)?
    • Are there configurable thresholds or hardcoded values?
    • What category should this analyzer belong to?
  3. Determine dependencies needed:

    • Configuration values? → Need scopeConfig dependency
    • Database queries? → Need resourceConnection dependency
    • File operations? → Need filesystem dependency
    • Module status? → Need moduleList or moduleManager dependency

Phase 2: Design

Before coding, state your design decisions:

DESIGN PLAN:
- Analyzer name: [DescriptiveName]Analyzer
- Category: [category-name]
- Interfaces: AnalyzerCheckInterface [+ ConfigAwareInterface] [+ DependencyAwareInterface]
- Dependencies needed: [list]
- Detection logic: [brief description]
- Issue priority: [high/medium/low] because [reason]

Read the full file on GitHub · 532 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. 11d ago First seen · 532 lines · 64 tokens per session scan A e3e1b39a0ef2

Subscribe to this mod's changes

analyzer-creator is an agent published in the GitHub repository magendooro/n98-magerun2-performance-review (22 stars, last pushed 9mo ago), licensed MIT. It adds 64 tokens to every session and 3,757 once invoked, about $0.0003 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

shopify-app-architect

Use when starting a new Shopify app or designing a major feature. Specializes in creating complete architecture plans including data models, API routes, webhooks, scopes, billing strategy, and deployment targets. Route here for architecture approval workflows.

khadinakbarlabs/shopify-app-builder · 52 tokens

polar-payments-specialist

Use this agent when you need to integrate, configure, or troubleshoot Polar Payments in a Next.js application. This includes setting up checkout flows, implementing webhooks, managing subscriptions, configuring products and benefits, handling license keys, implementing usage-based billing, or resolving any…

mars-mx/vibesaas · 404 tokens

meta-agent

Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent.

lroy-stack/ai-pod-store · 43 tokens

bug-investigator

Use this agent to investigate a single failing E2E test. Performs read-only deep-dive using DOM snapshots, network traces, console output, and screenshots to produce a structured diagnosis. Never modifies code. Examples: Context: A test failure needs root cause analysis. user: 'Investigate why the checkout test at…

kaizen-yutani/playwright-autopilot · 0 tokens

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens