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.
npx agentmods add commands/talayash/spring-fleet/impactgit clone --depth 1 https://github.com/talayash/spring-fleetWhat 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 | $0.00030 | $0.00362 |
| Opus 5 | $0.00015 | $0.00181 |
| Sonnet 5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
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 2d 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.
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:
- Locate
spring-fleet.config.json(cwd, else suggest/fleet-init). ReadreposRoot,services,sharedLibs, andproxyLib— these constrain where consumers can live. - Use the tracing-across-services skill (impact is the inverse of trace: you start from a shared symbol and fan outward through every consumer).
- 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. - 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.
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.
- 2d ago First seen · 28 lines · 30 tokens per session scan A e5d1cc8e6bfa
impact is a command published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 362 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-31.
Other commands, from other repositories
seo-drift
Compare two SEO snapshots (GSC / GSC AI Performance / rank tracker / AEO probe) and surface top movers per metric with auto-classification — growth / decline / reshuffle / stable / new / lost.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
ros-first-dollar
Step-by-step playbook to get your first paying customer.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.