A command that measures the likely impact of changing or deleting a file by finding dependents, coupling, and dependency cycles.

Use it before refactoring or deleting a file to decide whether the work is local, requires updating and testing dependents, or needs a larger structural change.

It shows whether an apparently small change could affect many other parts of a project.

impact — Command for Claude Code by RayforceDB/raysense

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/RayforceDB/raysense

Made for: Claude Code.

Or install raysense, the plugin that ships this one along with the rest of its 6 skills, 6 commands, 1 MCP server.

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/rayforcedb/raysense/impact/github.svg)](https://agentmods.dev/commands/rayforcedb/raysense/impact)

Your own site

<a href="https://agentmods.dev/commands/rayforcedb/raysense/impact"><img src="https://agentmods.dev/badge/commands/rayforcedb/raysense/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/rayforcedb/raysense/impact"><img src="https://agentmods.dev/badge/commands/rayforcedb/raysense/impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 203 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.00023	$0.00203
Opus 5.5	$0.00009	$0.00081
Sonnet 5.5	$0.00005	$0.00041
Haiku 4.5	$0.00002	$0.00020

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

Security

Grade A, and why

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

claude-plugin/commands/impact.md · 15 lines

What it actually says

Compute the structural impact of changing $2 in the project at $1.

If $1 is empty, treat the project root as the current working directory.

Call raysense_blast_radius with path: $1 and file: $2 to enumerate direct and transitive dependents.
Call raysense_coupling with path: $1 to read the fan-in / fan-out profile for $2.
Call raysense_cycles with path: $1 to check whether $2 participates in any cycle.

Finish with a verdict: is changing $2 a local edit, a coupled edit (touch-and-test the dependents), or a structural edit (cycle / high fan-in — split the work)?

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.

1mo ago First seen · 15 lines · 23 tokens per session scan A 47dfb0ae8786

Subscribe to this mod's changes

impact is a command published in the GitHub repository RayforceDB/raysense (13 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 203 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-08-30.

Claude Code Debugging ai-agents claude-agent code-architecture code-quality dependency-graph

deep-code-analysis

Comprehensive codebase investigation using research-expert for documentation, explore-codebase for structure, and deep analysis. Perfect for understanding complex systems.

fusengine/agents · 28 tokens

watch

Check for Claude Code updates, detect breaking changes, analyze plugin compatibility, and optionally gather community pulse via Exa.

fusengine/agents · 23 tokens

test-and-fix

Run tests, auto-fix fmt and lint, and fix failures until green or stuck.

solanabr/solana-ai-kit · 17 tokens

improve

/improve Scan and fix all improvement categories /improve arch Architectural improvements only /improve duplication Duplicate code / abstraction consolidation /improve quality Code quality (GuardLoop patterns GL-01 through GL-10) /improve security Security posture improvements /improve --dry-run Show what would be…

samibs/skillfoundry · 0 tokens

ops

You are the Ops Tooling Generator, an operational tooling specialist. You generate production-ready admin panels, debug overlays, and feedback systems for completed projects.