analyze-file

analyze-file is a command for Claude Code from rubenCodeforges/codeforges-claude-plugin. It costs 17 tokens per session (106 once invoked), scanned A, original, MIT.

A command for getting a detailed review of one specified code file, including its purpose, structure, dependencies, usage, quality, possible issues, and related tests.

In plain words
What is it for?
Use it to understand an unfamiliar file, find its imports and callers, assess its code, and identify improvements or related files.
Why use it?
It saves time when one file needs a thorough examination instead of a quick summary.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions subagents.

Good fit Use it to understand an unfamiliar file, find its imports and callers, assess its code, and identify improvements or related files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/rubencodeforges/codeforges-claude-plugin/analyze-file
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/rubenCodeforges/codeforges-claude-plugin

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 analyze-file

README.md
[![agentmods](https://agentmods.dev/badge/commands/rubencodeforges/codeforges-claude-plugin/analyze-file/github.svg)](https://agentmods.dev/commands/rubencodeforges/codeforges-claude-plugin/analyze-file)
Your own site
<a href="https://agentmods.dev/commands/rubencodeforges/codeforges-claude-plugin/analyze-file"><img src="https://agentmods.dev/badge/commands/rubencodeforges/codeforges-claude-plugin/analyze-file/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 analyze-file

Your own site · 80×15
<a href="https://agentmods.dev/commands/rubencodeforges/codeforges-claude-plugin/analyze-file"><img src="https://agentmods.dev/badge/commands/rubencodeforges/codeforges-claude-plugin/analyze-file.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 106 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00106
Opus 5.5 $0.00007 $0.00042
Sonnet 5.5 $0.00003 $0.00021
Haiku 4.5 $0.00002 $0.00011

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

Security

Grade A, and why

analyze-file 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.

commands/analyze-file.md · 18 lines

What it actually says

Invoke the @code-analyst sub-agent to perform a comprehensive analysis of the specified file.

The analysis should include:

  • File purpose and responsibility
  • Structure (functions, classes, exports)
  • Dependencies (external and internal)
  • Usage analysis (where this file is imported)
  • Code quality assessment
  • Potential issues and improvements
  • Related files (tests, dependencies)

Provide the file path after the command.

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. 1mo ago First seen · 18 lines · 17 tokens per session scan A eef186b5ba54

Subscribe to this mod's changes

analyze-file is a command published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (3 stars, last pushed 10mo ago), licensed MIT. It adds 17 tokens to every session and 106 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-31.