impact

impact is a skill for Claude Code from talayash/spring-fleet. It costs 32 tokens per session (427 once invoked), scanned A, original, MIT.

A cross-repository impact finder for shared-library symbols, files, and service API endpoints. It searches the fleet for consumers and groups the results by service with file and line references.

In plain words
What is it for?
Use it to find every service using a class, method, constant, shared file, or endpoint, and to highlight uses in request handlers, schedulers, event handlers, public APIs, or persisted data.
Why use it?
Changing shared code or a public API can affect many applications, including ones that are easy to overlook. A consumer list shows the likely blast radius before editing.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

Part of the spring-fleet plugin — 11 skills, 3 agents, 1 MCP server shipped together

Good fit Use it to find every service using a class, method, constant, shared file, or endpoint, and to highlight uses in request handlers, schedulers, event handlers, public APIs, or persisted data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/talayash/spring-fleet/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.

Any agent
npx skills add talayash/spring-fleet --skill impact
Clone the repo
git clone --depth 1 https://github.com/talayash/spring-fleet

Made for: Claude Code.

Or install spring-fleet, the plugin that ships this one along with the rest of its 11 skills, 3 agents, 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.

agentmods badge for impact

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/talayash/spring-fleet/impact"><img src="https://agentmods.dev/badge/skills/talayash/spring-fleet/impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 427 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.00032 $0.00427
Opus 5.5 $0.00013 $0.00171
Sonnet 5.5 $0.00006 $0.00085
Haiku 4.5 $0.00003 $0.00043

Measured 1mo ago against content hash f38cdcbe3f18, 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.

skills/impact/SKILL.md · 34 lines

What it actually says

Compute the cross-fleet blast radius of a change.

Input: $ARGUMENTS: one of:

  • a symbol (class, method, function, constant) from a shared lib (e.g. OrderEntity, core-lib.util.RetryPolicy.retry)
  • a file path in a shared lib (e.g. core-lib/src/main/java/.../RetryPolicy.java)
  • a published API endpoint owned by a service (e.g. POST /payment-v1/charge)

Steps:

  1. Locate spring-fleet.config.json (cwd, else suggest /fleet-init). Read reposRoot, services, sharedLibs, and proxyLib; these constrain where consumers can live.
  2. Use the tracing-across-services skill (impact is the inverse of trace: you start from a shared symbol and fan outward through every consumer).
  3. Dispatch the impact-analyzer agent with the config path and $ARGUMENTS. It searches every service repo (and the proxy-lib, if any) for usages and returns a grouped impact list.
  4. Present a per-service consumer count plus the citation list. Highlight any service that calls the symbol in a hot path (controller, scheduler, event handler) and any consumer that touches a public API or persisted data shape; those carry the highest change cost.

Outside Claude Code

  • $ARGUMENTS is the text the user supplied with the request.
  • No plugin subagents (Codex): read agents/impact-analyzer.md under the plugin root (two directories above this SKILL.md) and do that work yourself instead of dispatching.
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. 1mo ago First seen · 34 lines · 32 tokens per session scan A f38cdcbe3f18

Subscribe to this mod's changes

impact is a skill published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 427 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-09-30.

Related

Other skills, from other repositories

safe-refactoring

Use when restructuring, renaming, moving, or extracting code that already works — before making the first edit.

yuchi-chang/no-cape · 25 tokens

audit

Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.

oliver-kriska/claude-elixir-phoenix · 35 tokens

security-architecture-review

Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…

cbrock84/headcount · 78 tokens

operating-cadence

Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…

cbrock84/headcount · 95 tokens

debug

Systematically diagnose and resolve bugs through conversational investigation and root cause analysis.

rsmdt/the-startup · 15 tokens

improve

Find deepening opportunities in a codebase — refactors that turn shallow modules into deep ones for better testability and AI-navigability. Use when the user wants to improve architecture, surface architectural friction, consolidate tightly-coupled modules, find shallow abstractions or leaky seams, or make code more…

rsmdt/the-startup · 99 tokens