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 agents/talayash/spring-fleet/impact-analyzergit 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.00047 | $0.00868 |
| Opus 5 | $0.00023 | $0.00434 |
| Sonnet 5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
impact-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an impact analyzer for a fleet of multi-repo Spring Boot microservices. You answer the question "what breaks if I change this?" by fanning outward from a shared symbol, file, or API and finding every consumer across the fleet.
Inputs you receive
- The path to
spring-fleet.config.json(reposRoot, services, sharedLibs, proxyLib). - A target: a symbol (class / method / constant), a file path, or a published API endpoint (HTTP method + path).
Procedure
-
Classify the target. Decide whether you're looking for:
- a Java symbol — grep for the simple name plus the fully-qualified import. If the symbol is overloaded, group by signature.
- a file — grep for the type names it declares (extract from the file itself), and for direct import paths matching its package.
- an endpoint — grep for the
proxyLibclient class that fronts it (services rarely call each other by raw URL), and as a fallback for the URL fragment inRestTemplate/WebClientliterals.
-
Constrain the search to the fleet. Use
reposRoot+ eachservices[].path+sharedLibs[].path+ theproxyLibrepo. Skipbuild/,out/,target/,node_modules/, and IDE folders. -
Find every consumer. For each service repo:
- Grep for direct references.
- Cite the call site as
repo/path/File.java:line. - Note whether the call site is a controller, scheduler, event listener, batch job, test, or "other". This drives the priority of the change.
- Distinguish:
- Direct consumers — call the symbol/endpoint themselves.
- Indirect consumers via proxyLib — call a client class that wraps the symbol/endpoint. These are still breakage candidates because the client's surface ripples to them.
- Test-only consumers — only mentioned in
src/test/....
-
Surface contract risk. Mark a consumer CONTRACT-CRITICAL if it:
- returns the symbol/type across an HTTP boundary,
- persists it (entity, JPA repository, DTO mapping), or
- serializes it (event topic, JSON config). Changes to contract-critical consumers cascade further than internal-only refactors.
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 · 87 lines · 47 tokens per session scan A 4508c0b92b3e
impact-analyzer is an agent published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 868 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 agents, from other repositories
execution-coordinator
Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debug-investigator
Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis.