report

report is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 17 tokens per session (401 once invoked), scanned A, original, Apache-2.0.

A project analytics command that combines Git history, code measurements, dependency checks, tests, and documentation checks into a health report. Git is the version-control system used to track code changes.

In plain words
What is it for?
Use it to report contributor activity, recent change volume, lines of code, test ratios, long functions, TODO comments, outdated or vulnerable dependencies, test results, and documentation coverage.
Why use it?
It gathers several indicators in one report so teams can see activity, maintainability, dependency risk, test health, and documentation gaps.

Command

Part of the analytics-reporter plugin — 2 commands shipped together

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 commands/rohitg00/awesome-claude-code-toolkit/report
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install analytics-reporter, the plugin that ships this one along with the rest of its 2 commands.

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 report

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/report.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/report)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/report"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/report.svg" alt="Measured on agentmods" 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 401 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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00401
Opus 5 $0.00009 $0.00200
Sonnet 5 $0.00003 $0.00080
Haiku 4.5 $0.00002 $0.00040

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

Security

Grade A, and why

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

plugins/analytics-reporter/commands/report.md · 54 lines

What it actually says

Generate a project analytics report covering code quality, velocity, and health metrics.

Steps

  1. Gather git statistics:
    • git shortlog -sn --no-merges for contributor activity.
    • git log --format='%ai' --since='30 days ago' for commit frequency.
    • git diff --stat HEAD~50 for recent change volume.
  2. Analyze code quality metrics:
    • Lines of code by language using file extensions.
    • Test-to-code ratio (test files vs source files).
    • Average file size and function length.
    • TODO/FIXME/HACK comment count.
  3. Check dependency health:
    • Total dependencies (direct and transitive).
    • Outdated packages count.
    • Known vulnerability count.
  4. Measure test health:
    • Run test suite and capture pass/fail ratio.
    • Calculate approximate coverage if coverage tool exists.
  5. Assess documentation coverage:
    • README completeness check.
    • API documentation presence.
    • Inline documentation density.
  6. Compile findings into a structured report.

Format

Project Health Report - <date>

Code: <N> files, <N> LOC across <N> languages
Tests: <N> tests, <pass rate>% passing
Deps: <N> direct, <N> outdated, <N> vulnerable
Activity: <N> commits in last 30 days by <N> contributors

Score: <A/B/C/D/F>
Top issues:
  1. <most impactful issue>
  2. <second most impactful>

Rules

  • Use objective metrics, not subjective assessments.
  • Compare against industry benchmarks where possible.
  • Highlight trends (improving/declining) over the last 30 days.
  • Keep the report under 100 lines for quick consumption.
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. 4d ago First seen · 54 lines · 17 tokens per session scan A e5dc36689e26

Subscribe to this mod's changes

report is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,585 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 401 once invoked, about $0.0001 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-30.