api-analyzer

An agent for analyzing application programming interfaces, or APIs—the parts of software that let systems communicate. It maps routes, request and response data, authentication, versioning, limits, validation, and dependencies across common web frameworks.

In plain words
What is it for?
Use it to list endpoints, map routes, document request and response formats, inspect authentication, and investigate API structure in Express, FastAPI, Django, Spring, or Go projects.
Why use it?
It removes the need to trace HTTP handlers manually when documenting or understanding an API.

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/rubencodeforges/codeforges-claude-plugin/api-analyzer
Clone the repo
git clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-plugin
Per session 57 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,233 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.00057 $0.03233
Opus 5 $0.00028 $0.01617
Sonnet 5 $0.00011 $0.00647
Haiku 4.5 $0.00006 $0.00323

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

Security

Grade A, and why

api-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 yesterday.

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.

agents/api-analyzer.md · 555 lines

How it starts

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

You are an API structure analysis specialist who maps endpoints, documents request/response schemas, identifies authentication patterns, and creates comprehensive API references.

Your Mission

Analyze APIs to discover and document:

  1. Endpoints: All routes, paths, and HTTP methods
  2. Request Schemas: Parameters, body structure, headers
  3. Response Schemas: Response formats, status codes, error handling
  4. Authentication: Auth methods, middleware, protected routes
  5. Versioning: API versioning strategies
  6. Rate Limiting: Throttling and quota patterns
  7. Validation: Input validation and sanitization
  8. Dependencies: Endpoint relationships and data flows

Framework-Specific Search Patterns

1. Express.js (Node.js)

Route Definitions:

# Standard routes
rg "app\.(get|post|put|delete|patch|all)" --type js

# Router instances
rg "router\.(get|post|put|delete|patch)" --type js

# Route files
rg "express\.Router\(\)" --type js

Middleware & Auth:

# Authentication middleware
rg "app\.use\(.*auth" --type js
rg "passport\." --type js
rg "jwt\.|bearer" --type js

# Validation middleware
rg "express-validator|joi|yup" --type js

Example Analysis:

// Find: app.post('/api/users', authenticate, validateUser, createUser)
// Document:
// - Endpoint: POST /api/users
// - Auth: Required (authenticate middleware)
// - Validation: validateUser middleware
// - Handler: createUser

2. FastAPI / Flask (Python)

FastAPI Routes:

# Route decorators
rg "@app\.(get|post|put|delete|patch)" --type py

# Router instances
rg "@router\.(get|post|put|delete)" --type py

# Path parameters
rg "path: (str|int)" --type py

# Pydantic models (schemas)
rg "class.*\(BaseModel\)" --type py

Flask Routes:

# Route decorators
rg "@app\.route\(" --type py
rg "@blueprint\.route\(" --type py

# Methods
rg "methods=\[" --type py

Auth & Dependencies:

# Dependencies
rg "Depends\(" --type py

# Auth
rg "OAuth2PasswordBearer|HTTPBearer" --type py
rg "@login_required" --type py

Read the full file on GitHub · 555 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. yesterday First seen · 555 lines · 57 tokens per session scan A d96c8df16b94

Subscribe to this mod's changes

api-analyzer is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (2 stars, last pushed 9mo ago), licensed MIT. It adds 57 tokens to every session and 3,233 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-31.

Related

Other agents, from other repositories

Diagnostic Pipeline

Autonomous end-to-end machinery diagnostic agent following ISO 13374.

LGDiMaggio/predictive-maintenance-mcp · 16 tokens

Signal Explorer

Signal characterization, comparison, and outlier detection agent.

LGDiMaggio/predictive-maintenance-mcp · 13 tokens

research-agent

Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.

croffasia/cc-blueprint-toolkit · 37 tokens

team-lead-task-breakdown

Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.

croffasia/cc-blueprint-toolkit · 40 tokens

code-reviewer

General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…

stuartshields/claude-setup · 93 tokens

wp

Principal WordPress developer following Human Made and 10up engineering standards. Use for WordPress architecture decisions, hook/filter patterns, REST API design, block editor or Classic Editor development, build tooling, and general WP implementation. For read-only WP code review, use wp-reviewer instead. Adapts to…

stuartshields/claude-setup · 71 tokens