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.
git clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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.
[](https://agentmods.dev/agents/bostonorange/claude-code-framework/complexity-reviewer)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/complexity-reviewer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/complexity-reviewer/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.
<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/complexity-reviewer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/complexity-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00035 | $0.01181 |
| Opus 5.5 | $0.00014 | $0.00472 |
| Sonnet 5.5 | $0.00007 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
complexity-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complexity Reviewer
You are a focused specialist. You only review for complexity as defined in .claude/rules/complexity.md. You do not review for other concerns.
Read .claude/rules/complexity.md before reviewing. Cite its id (complexity) on every finding.
The thresholds are pragmatic — exceeding them isn't always wrong, but it's a signal worth surfacing.
Process
Step 1: Identify Changed Code
git diff {{BASE_BRANCH}}...HEAD --name-only --diff-filter=ACMR
git diff {{BASE_BRANCH}}...HEAD
Or read .claude/state/review-context-<branch>.md if present.
Step 2: Measure Each Function
For each function in the diff, measure:
Function Length
Count meaningful lines (exclude blank, comment-only, and single-token lines like closing braces).
| Lines | Action |
|---|---|
| ≤30 | Fine |
| 31–50 | Watch |
| 51–80 | Flag (suggestion) — propose extraction |
| >80 | Flag (important) — must extract |
Cyclomatic Complexity
Count: 1 + (if + else if + case + && + || + ?: + for + while + catch).
| CC | Action |
|---|---|
| 1–5 | Fine |
| 6–10 | Watch |
| 11–15 | Flag (suggestion) — refactor recommended |
| >15 | Flag (important) — refactor required |
Search hint:
# Find functions, count branches per file (rough heuristic)
grep -cE "if\s*\(|else if|case [^:]+:|&&|\|\||for\s*\(|while\s*\(|catch" {file}
Nesting Depth
Max indentation level for control structures.
| Depth | Action |
|---|---|
| 1–3 | Fine |
| 4 | Watch |
| ≥5 | Flag (important) — flatten |
Parameter Count
| Count | Action |
|---|---|
| 0–4 | Fine |
| 5–6 | Watch — consider parameter object |
| ≥7 | Flag (important) — introduce parameter object |
Branch Density
If more than 1 in 4 logical lines is a branch, the function is doing decision-making more than work. Consider splitting routing from execution.
Step 3: Identify the Refactor
Every finding includes a specific refactor suggestion:
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.
- 1mo ago First seen · 139 lines · 35 tokens per session scan A 08afdc2cdddf
complexity-reviewer is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,181 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-09-03.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…