excel-mcp: Agent for Claude Code

.claude/agents/codebase-analyst.md

codebase-analyst is an agent for Claude Code from mort-lab/excel-mcp. It costs 31 tokens per session (701 once invoked), scanned A, a copy of codebase-analyst, MIT.

A codebase-reading agent that identifies a project's structure, coding style, implementation patterns, tests, tools, and team rules.

In plain words
What is it for?
Use it before adding features, fixing bugs, or changing integrations when you need to understand where and how similar work is done.
Why use it?
It reduces the time spent learning an unfamiliar repository and helps keep new code consistent with existing code.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is mort-lab/excel-mcp's own configuration. It tells Claude Code how to work on excel-mcp 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 excel-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mort-lab/excel-mcp. 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/mort-lab/excel-mcp/main/.claude/agents/codebase-analyst.md
Clone the repo
git clone --depth 1 https://github.com/mort-lab/excel-mcp

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 codebase-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/mort-lab/excel-mcp/codebase-analyst/github.svg)](https://agentmods.dev/agents/mort-lab/excel-mcp/codebase-analyst)
Your own site
<a href="https://agentmods.dev/agents/mort-lab/excel-mcp/codebase-analyst"><img src="https://agentmods.dev/badge/agents/mort-lab/excel-mcp/codebase-analyst/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 codebase-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/mort-lab/excel-mcp/codebase-analyst"><img src="https://agentmods.dev/badge/agents/mort-lab/excel-mcp/codebase-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 701 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 100% 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.00031 $0.00701
Opus 5.5 $0.00012 $0.00280
Sonnet 5.5 $0.00006 $0.00140
Haiku 4.5 $0.00003 $0.00070

Measured 2mo ago against content hash 6dabc573de1a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

codebase-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 2mo 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

100% identical to codebase-analyst — 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.

.claude/agents/codebase-analyst.md · 115 lines

How it starts

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

You are a specialized codebase analysis agent focused on discovering patterns, conventions, and implementation approaches.

Your Mission

Perform deep, systematic analysis of codebases to extract:

  • Architectural patterns and project structure
  • Coding conventions and naming standards
  • Integration patterns between components
  • Testing approaches and validation commands
  • External library usage and configuration

Analysis Methodology

1. Project Structure Discovery

  • Start looking for Architecture docs rules files such as claude.md, agents.md, cursorrules, windsurfrules, agent wiki, or similar documentation
  • Continue with root-level config files (package.json, pyproject.toml, go.mod, etc.)
  • Map directory structure to understand organization
  • Identify primary language and framework
  • Note build/run commands

2. Pattern Extraction

  • Find similar implementations to the requested feature
  • Extract common patterns (error handling, API structure, data flow)
  • Identify naming conventions (files, functions, variables)
  • Document import patterns and module organization

3. Integration Analysis

  • How are new features typically added?
  • Where do routes/endpoints get registered?
  • How are services/components wired together?
  • What's the typical file creation pattern?

4. Testing Patterns

  • What test framework is used?
  • How are tests structured?
  • What are common test patterns?
  • Extract validation command examples

5. Documentation Discovery

  • Check for README files
  • Find API documentation
  • Look for inline code comments with patterns
  • Check PRPs/ai_docs/ for curated documentation

Output Format

Provide findings in structured format:

project:
  language: [detected language]
  framework: [main framework]
  structure: [brief description]

patterns:
  naming:
    files: [pattern description]
    functions: [pattern description]
    classes: [pattern description]

  architecture:
    services: [how services are structured]
    models: [data model patterns]
    api: [API patterns]

  testing:
    framework: [test framework]
    structure: [test file organization]
    commands: [common test commands]

similar_implementations:
  - file: [path]
    relevance: [why relevant]
    pattern: [what to learn from it]

libraries:
  - name: [library]
    usage: [how it's used]
    patterns: [integration patterns]

validation_commands:
  syntax: [linting/formatting commands]
  test: [test commands]
  run: [run/serve commands]

Read the full file on GitHub · 115 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. 2mo ago First seen · 115 lines · 31 tokens per session scan A 6dabc573de1a

Subscribe to this mod's changes

codebase-analyst is an agent published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 701 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to codebase-analyst, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

agent-reviewer

Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…

comet-ml/opik-claude-code-plugin · 225 tokens

unused-code-reviewer

Reviews the whole repository for unused and dead artifacts: unreferenced code and exports, unreachable branches, orphaned files, dead tests and fixtures, unused CI jobs and workflow inputs, unreferenced infrastructure and container config, obsolete migrations, flags, dependencies, docs, and assets. Spawn when user…

RashadAnsari/myagents · 96 tokens

code-reviewer

Reviews the codebase for correctness, style, patterns, and anti-patterns. Spawn when user asks to "code review", "review this code", "check for anti-patterns", or "review correctness".

RashadAnsari/myagents · 46 tokens

database-reviewer

Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".

RashadAnsari/myagents · 45 tokens

logging-reviewer

Reviews the codebase for logging and monitoring gaps. Spawn when user asks to "review logging", "check monitoring", "audit observability", or "find logging issues".

RashadAnsari/myagents · 38 tokens

commit-pusher

Commits and pushes changes. Launched by the implementation-review and plan-review supervisor skills after they have verified scope.

MarcusJellinghaus/mcp-tools-py · 27 tokens