What is crap-analyzer?

A code-risk checker that measures how difficult recently changed functions are to test and maintain. It uses code complexity and test coverage across several programming languages.

Reviewing changed code, finding functions that may need refactoring, discovering the project's coverage command, and suggesting test stubs.

It helps identify changed functions where complicated code and weak test coverage create a higher risk of bugs.

crap-analyzer — Plugin by swingerman

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.

Claude Code

/plugin marketplace add swingerman/engineer

agentmods

npx agentmods add plugins/swingerman/engineer/crap-analyzer

Clone the repo

git clone --depth 1 https://github.com/swingerman/engineer

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

crap-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.

crap-analyzer/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "crap-analyzer",
  "version": "0.1.1",
  "description": "Analyze recently-changed code for Change Risk Anti-Patterns. Computes CRAP per changed function across TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, and PHP. Auto-discovers how the repo generates coverage and proposes refactors + test stubs.",
  "author": {
    "name": "Miklos Szanyi",
    "url": "https://github.com/swingerman"
  },
  "homepage": "https://github.com/swingerman/engineer/tree/main/crap-analyzer",
  "repository": "https://github.com/swingerman/engineer",
  "license": "MIT",
  "keywords": ["code-quality", "testing", "coverage", "refactoring", "cyclomatic-complexity", "crap"]
}

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.

2d ago First seen · 14 lines scan A 3056f0a168d9

Subscribe to this mod's changes

crap-analyzer is a plugin published in the GitHub repository swingerman/engineer (144 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Languages Mobile Testing acceptance testing ai-development atdd bdd claude-code claude-code-plugin

crap-analyzer

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

flutter-riverpod-drift

xcode-build-skills

goldie

ios

swift-architecture-skill

uizze