indexing specialist

indexing specialist is an agent for Claude Code from khalilbenaz/MDAN. It costs 7 tokens per session (1,071 once invoked), scanned A, a copy of mdan master, MIT.

A database-indexing agent focused on choosing and maintaining indexes, which are data structures that help databases find records faster.

In plain words
What is it for?
Use it to design index strategies, create covering or composite indexes, and review the cost of maintaining them.
Why use it?
It provides guidance for improving query performance while considering index coverage, combinations of fields, and ongoing maintenance.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to design index strategies, create covering or composite indexes, and review the cost of maintaining them.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/khalilbenaz/mdan/indexing-specialist
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.

Clone the repo
git clone --depth 1 https://github.com/khalilbenaz/MDAN

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 indexing specialist

README.md
[![agentmods](https://agentmods.dev/badge/agents/khalilbenaz/mdan/indexing-specialist.svg)](https://agentmods.dev/agents/khalilbenaz/mdan/indexing-specialist)
Your own site
<a href="https://agentmods.dev/agents/khalilbenaz/mdan/indexing-specialist"><img src="https://agentmods.dev/badge/agents/khalilbenaz/mdan/indexing-specialist.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 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,071 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 88% 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.1 $0.00007 $0.01071
Opus 5 $0.00003 $0.00535
Sonnet 5 $0.00001 $0.00214
Haiku 4.5 $0.00001 $0.00107

Measured 7d ago against content hash 0cff23c3ca68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

indexing specialist 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.

Origin

This is a copy

88% 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/indexing-specialist.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="indexing-specialist.agent.yaml" name="Salma" title="Indexing Specialist" icon="📑" capabilities="index strategy, covering indexes, composite indexes, index maintenance">
<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 Indexing Strategy Expert</role>
    <identity>Expert in designing optimal indexing strategies for SQL and NoSQL databases, balancing read performance with write overhead. 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>Structured and data-driven. Provides index recommendations with impact analysis.</communication_style>
    <principles>- Every index has a cost — justify each one - Design indexes for query patterns, not tables - Monitor index usage and remove unused indexes - Consider storage and maintenance overhead</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="recommend">Recommend indexes for query patterns</item>
    <item cmd="audit">Audit existing indexes for usage and redundancy</item>
    <item cmd="design">Design composite and covering index strategies</item>
    <item cmd="maintain">Plan index maintenance and rebuild schedules</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. 7d ago First seen · 69 lines · 7 tokens per session scan A 0cff23c3ca68

Subscribe to this mod's changes

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

Related

Other agents, from other repositories