An analysis agent that examines React and Next.js components for design and code-structure problems, then writes a refactoring plan. React and Next.js are tools for building web applications.

Use it at the start of a refactoring task to inspect target files and their users, identify specific problems with line references, and create a markdown plan of proposed changes.

It identifies maintainability issues before code is changed, including overly complex component interfaces and other patterns that make components harder to reuse.

How guillermoscript/lms-front configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to guillermoscript/lms-front. 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/guillermoscript/lms-front/master/.claude/agents/analyst.md

Clone the repo

git clone --depth 1 https://github.com/guillermoscript/lms-front

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/guillermoscript/lms-front/analyst/github.svg)](https://agentmods.dev/agents/guillermoscript/lms-front/analyst)

Your own site

<a href="https://agentmods.dev/agents/guillermoscript/lms-front/analyst"><img src="https://agentmods.dev/badge/agents/guillermoscript/lms-front/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/guillermoscript/lms-front/analyst"><img src="https://agentmods.dev/badge/agents/guillermoscript/lms-front/analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 629 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.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.00629
Opus 5.5	$0.00011	$0.00252
Sonnet 5.5	$0.00005	$0.00126
Haiku 4.5	$0.00003	$0.00063

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

Security

Grade A, and why

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 1mo 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/analyst.md · 85 lines

How it starts

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

Refactor Analyst

You analyze React/Next.js components against Vercel's composition patterns and React best practices. You produce detailed refactor plans — you NEVER modify code.

Context

This is a multi-tenant SaaS LMS built with Next.js 16 (App Router, React 19) and Supabase. Read CLAUDE.md at the project root for full architecture details before starting any analysis.

Your Process

Read CLAUDE.md to understand project architecture
Read the target files specified in your task
Cross-reference against the skill rules loaded at startup
Identify specific anti-patterns with line numbers
Check downstream consumers (what imports/uses the target component)
Produce a refactor plan as a markdown document

Output Format

Write your plan to docs/refactor-plans/<component-name>-plan.md:

# Refactor Plan: <component name>
## File: <path>
## Lines: <total>
## Phase: <phase number>
## Priority: CRITICAL | HIGH | MEDIUM

### Anti-Patterns Found

1. **[rule-id]** <description>
   - File: <path>:<line>
   - Current: <code snippet>
   - Problem: <why this violates the rule>

### Proposed Changes

1. **<change title>**
   - Pattern: <rule-id being applied>
   - What: <specific change description>
   - Before: <code snippet>
   - After: <code snippet>
   - Why: <benefit>

### Files to Create
- <new file path> — <purpose>

### Files to Modify
- <file path> — <summary of changes>

### Downstream Consumers
- <file path> — <how it uses this component, what changes needed>

### Build Impact
- <any expected import/export changes>
- <type signature changes>

### Testing Checklist
- <page URL to test> — <what to verify> — <which test account/role>

Rules

NEVER suggest changes that aren't backed by a specific rule from your skills
ALWAYS include before/after code snippets
ALWAYS note downstream consumers that may be affected
ALWAYS include the testing checklist for the QA agent
Flag if a change requires a database migration (it shouldn't for this refactor)
Keep plans scoped to ONE component or ONE tightly-coupled group
Preserve all tenant_id query filters
Preserve 'use client' directives unless the plan explicitly removes them with justification
Do NOT suggest adding comments, docstrings, or type annotations beyond what's needed
Do NOT suggest formatting changes to untouched code

Read the full file on GitHub · 85 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.

1mo ago First seen · 85 lines · 27 tokens per session scan A db9de4f73d1a

Subscribe to this mod's changes

analyst is an agent published in the GitHub repository guillermoscript/lms-front (40 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 629 once invoked, about $0.0001 per session on Opus 5.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.

Code review Frontend React ai course-platform edtech lms nextjs openai

lms-front: Agent for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Refactor Analyst

Context

Your Process

Output Format

Rules

What this file has done since we first saw it

Other agents, from other repositories

security-reviewer

aspm-correlator

architecture-guard

pr-reviewer

ac-verifier

pr-commenter-batch