A Git activity report that reviews recent commits for signs of change-related risk.

Use it to examine risky commits, frequently changing files with many dependants, complexity growth, large changes, and areas needing better test coverage.

It helps focus review and testing on changes most likely to cause problems.

How suitable-adventures/suitable-loop configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to suitable-adventures/suitable-loop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/suitable-adventures/suitable-loop/main/.claude/commands/risk-report.md

Clone the repo

git clone --depth 1 https://github.com/suitable-adventures/suitable-loop

Made for: Claude Code.

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/commands/suitable-adventures/suitable-loop/risk-report/github.svg)](https://agentmods.dev/commands/suitable-adventures/suitable-loop/risk-report)

Your own site

<a href="https://agentmods.dev/commands/suitable-adventures/suitable-loop/risk-report"><img src="https://agentmods.dev/badge/commands/suitable-adventures/suitable-loop/risk-report/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/suitable-adventures/suitable-loop/risk-report"><img src="https://agentmods.dev/badge/commands/suitable-adventures/suitable-loop/risk-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 153 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00000	$0.00153
Opus 5.5	$0.00000	$0.00061
Sonnet 5.5	$0.00000	$0.00031
Haiku 4.5	$0.00000	$0.00015

Measured 2mo ago against content hash 18906dffdbe7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

risk-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 2mo 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.

.claude/commands/risk-report.md · 13 lines

What it actually says

Analyze recent git activity and produce a risk report.

Steps:

Use analyze_recent_changes on this repo (last 30 commits)
For the top 3 riskiest commits, use analyze_commit to get detailed breakdowns
Use hotspot_report on this repo to cross-reference with code hotspots

Then produce a report covering:

Top 5 riskiest commits with their risk scores and key factors (complexity delta, blast radius, churn, lines changed)
For each risky commit: what files were touched and why it's risky
Current hotspots: files that change frequently AND are heavily depended upon
Actionable recommendations: which changes deserve extra review, which areas need better test coverage

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.

2mo ago First seen · 13 lines · 0 tokens per session scan A 18906dffdbe7

Subscribe to this mod's changes

risk-report is a command published in the GitHub repository suitable-adventures/suitable-loop (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 153 tokens. 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 Git and workflow

risk-report next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
risk-reportsuitable-adventures/suitable-loop	Command	0	7mo ago	MIT	A	0	Claude Code
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
commitechoVic/blade-code	Command	181	24d ago	MIT	A	8	Claude Code
repo-audittractorjuice/arc-kit	Command	2.3k	2d ago	none	A	29	Claude Code
propsmill/infrahub-mcp	Command	10	yesterday	Apache-2.0	A	18	Claude Code
codex-reviewoalders/kitchen-sink	Command	5	4d ago	MIT	A	41	Claude Code

suitable-loop: Command for Claude Code