Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install code-metricsWrote 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/skills/melodic-software/claude-code-plugins/audit-size)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/audit-size"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/audit-size/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/skills/melodic-software/claude-code-plugins/audit-size"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/audit-size.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.00109 | $0.01575 |
| Opus 5.5 | $0.00044 | $0.00630 |
| Sonnet 5.5 | $0.00022 | $0.00315 |
| Haiku 4.5 | $0.00011 | $0.00158 |
Grade A, and why
audit-size 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
Current branch: !git branch --show-current 2>/dev/null || echo "unknown"
Purpose
Lines per file is the one measure on the operator's list with a crisp definition and no standard-backed file-level threshold. This skill reports the number, per file in the scope, beside a reference whose provenance is printed with it, and stops there: no pass or fail, no severity, no finding. Deciding what to do with a long file is the reader's call; the report gives them the number and the citation.
Two collectors, tried in order:
| Collector | Values per file | When |
|---|---|---|
scc |
lines_total, lines_blank, lines_comment, lines_code, lines_non_blank |
scc resolves on PATH |
| bundled counter | lines_total, lines_blank, lines_non_blank, labeled comment-agnostic |
always |
scc is used for line counting only; its complexity figure is never read, because it is a
substring count rather than cyclomatic complexity.
Every text file in scope is measured. The language lanes (TypeScript/JavaScript, Python, Bash,
Go, C#) are detected by extension, and everything else that is not binary (markdown, JSON, YAML,
PowerShell, a Makefile) lands in the catch-all other lane, which this measure serves and no
other does; lanes.other.enabled: false opts it out.
Run it
"${CLAUDE_SKILL_DIR}/scripts/audit-size.sh" # the change: diff from the merge-base plus uncommitted files
"${CLAUDE_SKILL_DIR}/scripts/audit-size.sh" src/ lib/util.py # explicit paths (a missing one is a usage error)
"${CLAUDE_SKILL_DIR}/scripts/audit-size.sh" --all # every tracked or untracked-but-not-ignored file
"${CLAUDE_SKILL_DIR}/scripts/audit-size.sh" --json --all src/ # the code-metrics/v2 document instead of markdown
Present the markdown report to the user as printed. It opens with the scope and a "Coverage of
this run" table (lane, collector, status, reason), then the reference with its provenance and
layer, then one row per file, longest first by lines_non_blank, with its values and whether it
is at or above the reference. Keep
the --json document when the numbers feed a comparison: /verification:measure metrics consumes
it when the verification plugin is installed (treat a report whose status is empty on either
side as INCONCLUSIVE); otherwise keep the JSON beside your notes and compare by hand.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed d439598c0093
- 16d ago Changed 88425fc9d858
- 17d ago Changed · -126 tokens per session 65c09d7b9246
- 23d ago Changed a0083e1031d7
- 1mo ago Changed · +9 lines · +14 tokens per session e07187386eeb
- 1mo ago Changed · +5 lines 2972855bcda7
- 1mo ago First seen · 93 lines · 221 tokens per session scan A 4aadf00faf97
audit-size is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 1,575 once invoked, about $0.0004 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-06.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
pass-function-as-arg
For generic algorithms: strategy pattern, callbacks, configurable behavior. Pass functions as parameters to customize algorithm behavior.
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.