icpg-impact

icpg-impact is a command for Claude Code from alinaqi/maggy. It costs 0 tokens per session (333 once invoked), scanned A, original, MIT.

A command that shows the blast radius of a code symbol or recorded project decision. Blast radius means the other code and planned work that may be affected if it changes.

In plain words
What is it for?
Use it to inspect callers and dependent intentions, review related contracts and tests, estimate change risk, and decide whether broader testing is needed.
Why use it?
It helps developers see dependencies and risks before editing an important function, class, file, or design decision.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to inspect callers and dependent intentions, review related contracts and tests, estimate change risk, and decide whether broader testing is needed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alinaqi/maggy/icpg-impact
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.

Clone the repo
git clone --depth 1 https://github.com/alinaqi/maggy

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.

agentmods badge for icpg-impact

README.md
[![agentmods](https://agentmods.dev/badge/commands/alinaqi/maggy/icpg-impact/github.svg)](https://agentmods.dev/commands/alinaqi/maggy/icpg-impact)
Your own site
<a href="https://agentmods.dev/commands/alinaqi/maggy/icpg-impact"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/icpg-impact/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.

agentmods 80×15 button for icpg-impact

Your own site · 80×15
<a href="https://agentmods.dev/commands/alinaqi/maggy/icpg-impact"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/icpg-impact.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 333 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00333
Opus 5 $0.00000 $0.00167
Sonnet 5 $0.00000 $0.00067
Haiku 4.5 $0.00000 $0.00033

Measured 9d ago against content hash 13625e7666eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

icpg-impact 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 9d 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.

commands/icpg-impact.md · 61 lines

What it actually says

/icpg-impact — Show Blast Radius

Show the blast radius of a ReasonNode or symbol — what depends on it, what breaks if it changes.


Usage

/icpg-impact <id-or-symbol>

  • If argument looks like a UUID (contains -), treat as ReasonNode ID
  • Otherwise, treat as symbol name and find its creating ReasonNode

Steps

1. Resolve target

# If ReasonNode ID
icpg query blast <id>

# If symbol name
icpg query risk <symbol-name>
# Then get the creating reason from the output
icpg query blast <creating-reason-id>

2. Display results

Format the output as:

BLAST RADIUS: <goal>
═══════════════════════════════════

Symbols ({N}):
  function validateToken (src/auth/service.ts)
  class AuthMiddleware (src/auth/middleware.ts)
  ...

Dependent Intents ({N}):
  a1b2c3d4 — Dashboard user session management
  e5f6g7h8 — Payment authorization flow
  ...

Contracts:
  INV: file_exists("src/auth/middleware.ts")
  POST: test_exists("src/auth/__tests__/service.test.ts")

Risk: {HIGH|MEDIUM|LOW} based on dependent count + drift history

3. Recommendations

If high risk (>5 dependents or active drift):

  • Suggest running full test suite before changes
  • Suggest creating a new ReasonNode with MODIFIES edge
  • Warn about function signatures to preserve
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. 9d ago First seen · 61 lines · 0 tokens per session scan A 13625e7666eb

Subscribe to this mod's changes

icpg-impact is a command published in the GitHub repository alinaqi/maggy (705 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 333 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-30.