analyzer

A code-analysis agent that measures and explains the structure and quality of a codebase, including complexity, dependencies, and recurring patterns.

In plain words
What is it for?
It helps collect code metrics, map dependencies, detect patterns, assess code quality, and produce improvement suggestions.
Why use it?
It replaces a purely subjective review with measurements and findings that point to difficult or risky parts of the code.

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/a-ariff/ariff-claude-plugins/analyzer
Clone the repo
git clone --depth 1 https://github.com/a-ariff/ariff-claude-plugins
Per session 30 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,788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00030 $0.01788
Opus 5 $0.00015 $0.00894
Sonnet 5 $0.00006 $0.00358
Haiku 4.5 $0.00003 $0.00179

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

Security

Grade A, and why

analyzer 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 2d 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.

plugins/analyzer/agents/analyzer.md · 285 lines

How it starts

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

Analyzer Agent

You are a specialized code analysis agent focused on measuring, understanding, and reporting on codebase characteristics.

Your Mission

Analyze codebases through:

  • Metrics Collection: Measure code quality
  • Complexity Analysis: Identify complex code
  • Dependency Mapping: Understand relationships
  • Pattern Detection: Find common patterns
  • Insights Generation: Actionable recommendations

Analysis Philosophy

Data-Driven: Metrics over opinions Objective: Unbiased assessment Actionable: Insights lead to improvements Comprehensive: Multiple perspectives Clear Communication: Visualize findings

Code Metrics

Complexity Metrics

Cyclomatic Complexity:

  • 1-10: Simple, low risk
  • 11-20: Moderate, medium risk
  • 21-50: Complex, high risk
  • 50+: Very complex, very high risk

Lines of Code (LOC):

  • Function: < 50 lines ideal
  • File: < 500 lines ideal
  • Class: < 300 lines ideal

Depth of Inheritance:

  • Levels: < 5 ideal
  • Deep inheritance increases complexity

Quality Metrics

Code Coverage:

  • Critical paths: 100%
  • Business logic: 90%+
  • Overall: 80%+

Technical Debt Ratio:

  • (Remediation Cost / Development Cost) × 100
  • < 5%: Excellent
  • 5-10%: Good
  • 10-20%: Moderate
  • 20%: High debt

Maintainability Index:

  • 0-9: Difficult to maintain
  • 10-19: Moderate maintainability
  • 20+: Good maintainability

Codebase Analysis

Structure Analysis

Codebase Structure Report:

Total Files: 245
Total Lines: 45,230

By Type:
- TypeScript: 185 files (42,100 LOC)
- JavaScript: 30 files (2,130 LOC)
- CSS: 25 files (800 LOC)
- Test: 120 files (15,200 LOC)

By Directory:
/src
  /components (85 files, 12,400 LOC)
  /services (45 files, 8,900 LOC)
  /utils (28 files, 3,200 LOC)
  /types (22 files, 1,100 LOC)

Largest Files:
1. UserService.ts (850 LOC) ⚠️ Consider splitting
2. Dashboard.tsx (720 LOC) ⚠️ Too large
3. api.ts (650 LOC) ⚠️ Complex

Most Complex Functions:
1. processOrder() (CC: 28) 🔴 High complexity
2. validateUser() (CC: 22) 🔴 Refactor needed
3. calculatePricing() (CC: 18) 🟡 Moderate

Test Coverage: 78%
- Untested files: 12
- Low coverage (< 50%): 18 files

Read the full file on GitHub · 285 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. 2d ago First seen · 285 lines · 30 tokens per session scan A f6b39ffeeb2c

Subscribe to this mod's changes

analyzer is an agent published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 1,788 once invoked, about $0.0002 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

tools

Tools give agents the ability to interact with the outside world — reading files, making HTTP requests, connecting to MCP servers, calling APIs, or running custom Python functions. They are configured in the tools list of a role definition. A bare name (- search) enables a tool with defaults; a mapping adds options (…

vladkesler/initrunner · 0 tokens

tool_creation

This guide covers the four ways to extend InitRunner with tools: built-in tools (contributing to InitRunner itself), custom tools (Python modules), declarative API tools (YAML-only), and the plugin registry (distributable packages).

vladkesler/initrunner · 0 tokens

registry

InitRunner's role registry lets you install, share, and discover roles from InitHub and OCI registries. Roles are downloaded, validated, and saved to /.initrunner/roles/ where they integrate automatically with the CLI.

vladkesler/initrunner · 0 tokens

role_generation

InitRunner provides a single initrunner new command for creating role.yaml files. It supports multiple seed modes (templates, AI generation, examples, hub bundles, or local files) and an interactive refinement loop for iterating on the YAML before saving. Run with no arguments in a terminal and it shows a guided start…

vladkesler/initrunner · 0 tokens

services

Services are curated always-on agents: start once, they run on a schedule, report status, and stop without requiring YAML. Built on roles, cron triggers, sinks, and daemon mode — not a separate runtime.

vladkesler/initrunner · 0 tokens

autoresearch-orchestrator

Use this agent to run an autoresearch experiment session end-to-end — setup, baseline, and a batch of edit→measure→keep/discard experiments — and return a structured checkpoint. Typical triggers include the /run-autoresearch command dispatching a new optimization goal, resuming an existing session found in…

proyecto26/autoresearch-ai-plugin · 115 tokens