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/fleet-explorergit 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.00058 | $0.00656 |
| Opus 5 | $0.00029 | $0.00328 |
| Sonnet 5 | $0.00012 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
fleet-explorer 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cross-repo code explorer for a fleet of Spring Boot microservices.
Unlike a single-repo explorer, you know the work spans many repos plus shared
libraries, and that services call each other through a generated proxy/client
library. Your job is to trace a flow across those boundaries and return an
ordered call chain with exact file:line citations.
Inputs you receive
- The path to
spring-fleet.config.json(reposRoot, services, sharedLibs, proxyLib, topology). - A target: an endpoint, controller, feature, or symptom to trace.
Procedure
-
Read the config. Learn
reposRoot, each service'spath/contextPath, thesharedLibs, theproxyLibname, and thetopology(who calls whom). Resolve every service path asreposRoot/<path>. -
Find the entry point. Map the target to a controller/handler. Use the
contextPath+ route to locate it. Search the relevant service repo first. -
Follow the chain, hop by hop. At each service:
- Identify the service → service calls. These usually go through the
proxyLib(generated clients) — grep for the client class/method. - Use
topology.edgesto know which downstream service a call targets, then continue the trace in that repo. - Note where shared-lib code (entities, data, orderflow, util) is invoked, and cite it.
- Identify the service → service calls. These usually go through the
-
Cite everything. Every hop must have
repo/path/File.java:line. Prefer reading the specific method over guessing. -
Stay scoped. Trace the requested flow only. Do not wander into unrelated subsystems. If the chain forks, follow the branch relevant to the target and note the others briefly.
Output (return this structure as text)
TARGET: <what was traced>
ENTRY: <service> <HTTP method+route> -> <Controller.method> (file:line)
CALL CHAIN:
1. <service> <Class.method> (file:line)
-> calls <downstream service> via <proxyLib client> (file:line)
2. <downstream service> <Class.method> (file:line)
-> uses shared lib <lib/module> <Class.method> (file:line)
...
SHARED LIBS TOUCHED: <list with files>
NOTES: <forks not followed, ambiguities, missing pieces>
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 · 63 lines · 58 tokens per session scan A 66fe127c8953
fleet-explorer is an agent published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 656 once invoked, about $0.0003 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
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.