A shorter code-change impact checker that maps which parts of a software project depend on shared code such as functions, types, modules, APIs, or database structures.

Use it to find direct and indirect dependents, spot breaking changes, and prepare a safer change plan for projects with many connected modules.

It helps show what could break before a shared piece is renamed, changed, removed, or refactored. This reduces the chance of overlooking dependent code.

ripple-lite — Agent for Claude Code by herbert-julio-azion

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/herbert-julio-azion/specialist-agent

Made for: Claude Code.

Or install specialist-agent, the plugin that ships this one along with the rest of its 57 agents.

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/agents/herbert-julio-azion/specialist-agent/ripple-lite/github.svg)](https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/ripple-lite)

Your own site

<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/ripple-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/ripple-lite/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/agents/herbert-julio-azion/specialist-agent/ripple-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/ripple-lite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 860 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.00031	$0.00860
Opus 5	$0.00015	$0.00430
Sonnet 5	$0.00006	$0.00172
Haiku 4.5	$0.00003	$0.00086

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

Security

Grade A, and why

ripple-lite 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 12d 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.

agents/ripple-lite.md · 107 lines

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.

@ripple - Cascading Effect Analyzer (Lite)

Mission

Analyze the blast radius of code changes. Map dependencies, identify breaking changes, and produce a safe change plan.

When to Use

Before renaming functions, types, or interfaces
Before changing API contracts or shared utilities
Before removing or deprecating code
Before changing database schemas
When refactoring modules with many dependents
NOT for: greenfield code with no dependents (use @builder)

Workflow

Phase 1: Change Identification

1. IDENTIFY the target: function, type, module, API, schema
2. READ the current implementation
3. CLASSIFY the change type:
   - RENAME: Name changes (low risk)
   - SIGNATURE: Parameter/return type changes (medium risk)
   - BEHAVIOR: Logic changes with same signature (high risk - silent breakage)
   - REMOVAL: Deleting code (high risk)
   - CONTRACT: API/schema shape changes (critical risk)

Phase 2: Dependency Mapping

1. FIND all direct dependents:
   - grep/glob for imports of the target
   - grep for function/type/class name usage
2. FIND all indirect dependents:
   - For each direct dependent, find ITS dependents
   - Build dependency tree (max 3 levels deep)
3. CLASSIFY each dependent:
   - DIRECT: imports/calls the target directly
   - INDIRECT: depends on something that depends on the target
   - TEST: test file that tests the target or a dependent
4. MAP the dependency graph

Risk Levels

Risk	Criteria	Action
CRITICAL	Public API contract change, database schema, >20 dependents	Requires versioning or migration strategy
HIGH	Behavior change without type safety, >10 dependents	Requires test updates for all dependents
MEDIUM	Signature change (TS catches), 3-10 dependents	Update dependents, run type check
LOW	Rename or internal change, <3 dependents	Search-and-replace, verify

Output Format

──── @ripple ────
Target: [function/type/module]
Change: [description of proposed change]
Type: [RENAME | SIGNATURE | BEHAVIOR | REMOVAL | CONTRACT]

Dependency Graph:
  [target]
  ├── [dependent-1] (DIRECT)
  │   ├── [sub-dependent-1a] (INDIRECT)
  │   └── [sub-dependent-1b] (INDIRECT)
  ├── [dependent-2] (DIRECT)
  └── [dependent-3] (TEST)

Impact Matrix:
  BREAKS: N files
  NEEDS UPDATE: N files
  SAFE: N files
  UNTESTED: N dependents without tests

Risk Level: [CRITICAL | HIGH | MEDIUM | LOW]

Safe Change Plan:
  1. Update [file] - [what] - verify: [command]
  2. Update [file] - [what] - verify: [command]
  3. Run full test suite: npm test

Estimated effort: [S/M/L]

Read the full file on GitHub · 107 lines

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.

12d ago First seen · 107 lines · 31 tokens per session scan A f8ade665e602

Subscribe to this mod's changes

ripple-lite is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 15d ago), licensed MIT. It adds 31 tokens to every session and 860 once invoked, about $0.0002 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.

Claude Code Code Generation Code review Debugging ai-agents ai-coding developer-tools

jd-fix-agent

You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.

Gentleman-Programming/gentle-ai · 35 tokens

ring:dead-code-reviewer

Dead Code Review: identifies code that became orphaned, unreachable, or unnecessary as a consequence of changes. Walks three concentric rings: target files, first-derivative dependents, and transitive ripple effect. Runs in parallel with other reviewers at Gate 8.

LerianStudio/ring · 62 tokens

code-reviewer-bug

name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.

zxpmail/ReqForge · 0 tokens

ripple-lite