A skill that measures source-code complexity and code size by reading a file's syntax tree, which is the structured form a parser builds from code.

Reporting cyclomatic complexity, physical lines of code, and logical lines of code for TypeScript, JavaScript, Python, Java, or C# files.

It replaces subjective estimates with repeatable measurements for each function in a supported source file.

analyze — Skill for Claude Code and Codex by ahernandez-developer: A skill that measures source-code complexity and code size…

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 skills/ahernandez-developer/claude-crap/analyze

Any agent

npx skills add ahernandez-developer/claude-crap --skill analyze

Clone the repo

git clone --depth 1 https://github.com/ahernandez-developer/claude-crap

Made for: Claude Code, Codex.

Or install claude-crap, the plugin that ships this one along with the rest of its 4 skills, 5 hooks, 1 MCP server.

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/skills/ahernandez-developer/claude-crap/analyze.svg)](https://agentmods.dev/skills/ahernandez-developer/claude-crap/analyze)

Your own site

<a href="https://agentmods.dev/skills/ahernandez-developer/claude-crap/analyze"><img src="https://agentmods.dev/badge/skills/ahernandez-developer/claude-crap/analyze.svg" alt="Measured on agentmods" height="20"></a>

Per session 191 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,325 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.

Model	Per session	Once invoked
Fable 5	$0.00191	$0.01325
Opus 5	$0.00096	$0.00662
Sonnet 5	$0.00038	$0.00265
Haiku 4.5	$0.00019	$0.00133

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

Security

Grade A, and why

analyze 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 4d 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.

plugin/skills/analyze/SKILL.md · 78 lines

How it starts

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

Analyze a source file with tree-sitter

Run the analyze_file_ast MCP tool from the claude-crap server against a user-supplied file and report deterministic AST metrics.

Arguments

The user supplies a file path as the argument, typed after the skill name:

/claude-crap:analyze src/index.ts
/claude-crap:analyze app/main.py
/claude-crap:analyze lib/foo.cs

Steps

Parse the file path. Take $ARGUMENTS as the path. Reject it with a friendly one-liner if it contains ../ — the server's workspace guard will reject path traversal attempts regardless, but failing fast in the skill is cleaner than surfacing a stack trace from the MCP layer.
Detect the language from the extension. Use this table:

Extension language argument

.ts / .tsx / .mts / .cts typescript

.js / .jsx / .mjs / .cjs javascript

.py python

.java java

.cs csharp

If the extension does not map to one of those five, tell the user which languages are supported and do not invoke the tool. Claude-sonar's tree-sitter engine is language-scoped; there is no "auto-detect from content" mode.
Invoke the MCP tool analyze_file_ast with filePath: "$ARGUMENTS" and the detected language.
Display file-level metrics first: physical LOC (every newline-terminated line including blanks and comments) and logical LOC (lines with at least one non-whitespace character). The delta between the two is an informal "comment density" signal.
Display a ranked function list, sorted by cyclomatic complexity descending. For each function, show:
- Function name (or <anonymous> if the tree-sitter grammar could not resolve a name)
- Start line → end line
- Cyclomatic complexity
- Physical line count (endLine - startLine + 1)

Extension	`language` argument
`.ts` / `.tsx` / `.mts` / `.cts`	`typescript`
`.js` / `.jsx` / `.mjs` / `.cjs`	`javascript`
`.py`	`python`
`.java`	`java`
`.cs`	`csharp`

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

4d ago First seen · 78 lines · 191 tokens per session scan A 78d1dbcba1c9

Subscribe to this mod's changes

analyze is a skill published in the GitHub repository ahernandez-developer/claude-crap (8 stars, last pushed 4mo ago), licensed MIT. It adds 191 tokens to every session and 1,325 once invoked, about $0.0010 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.

Analytics and metrics

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens