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 skills add talayash/spring-fleet --skill tracing-across-servicesgit clone --depth 1 https://github.com/talayash/spring-fleetWrote 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.
[](https://agentmods.dev/skills/talayash/spring-fleet/tracing-across-services)<a href="https://agentmods.dev/skills/talayash/spring-fleet/tracing-across-services"><img src="https://agentmods.dev/badge/skills/talayash/spring-fleet/tracing-across-services.svg" alt="Measured on agentmods" height="20"></a>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.00049 | $0.00491 |
| Opus 5 | $0.00024 | $0.00246 |
| Sonnet 5 | $0.00010 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
tracing-across-services 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 8d 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
Tracing a Flow Across a Service Fleet
A single feature often crosses several repos: an entry controller calls downstream services (usually through a generated proxy/client library), each of which leans on shared libraries. This skill reconstructs that chain.
Prerequisites
- A
spring-fleet.config.jsonexists (else run/fleet-init). It provides thereposRoot, services,sharedLibs,proxyLib, andtopology.
Procedure
-
Identify the target. An endpoint (
POST /order-v1/reserve), a controller, or a feature name. If ambiguous, locate candidate entry points first and confirm with the user. -
Dispatch the
fleet-exploreragent with the config path and the target. It knows the flow spans many repos, followsproxyLibclient calls across service boundaries usingtopology.edges, and returns an ordered call chain withfile:linecitations and the shared-lib code each hop touches. -
Read the chain critically. Confirm each hop's downstream target matches the topology. Where a hop is dynamic (reflection, event bus, conditional routing), the explorer marks it — resolve it by reading the dispatch site rather than guessing.
-
Present the result. Give the ordered chain entry → … → leaf, each step cited, plus a short summary of which services and shared-lib modules participate. Highlight the hops most relevant to the user's goal (e.g. where a change must be made, or where a failure could originate).
Tips
- The
proxyLibis the seam between services — grep it for the client class to find who calls whom when the topology is unclear. - Contract changes ripple through the
proxyLib: if a hop's request/response shape changes, the generated client (and every caller) is affected. - For "what breaks if I change this shared-lib code?", trace consumers outward from the shared module instead of inward from an endpoint.
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.
- 8d ago First seen · 46 lines · 49 tokens per session scan A 33178d708d44
tracing-across-services is a skill published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 491 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 skills, from other repositories
sofa-search
Search Stack Overflow for Agents (SOFA) for a peer-verified solution before solving from scratch. TRIGGER when: about to debug an unfamiliar error, integrate a new API/library, or research an unfamiliar pattern, and SOFA is configured. SKIP: trivial/familiar tasks; SOFA unconfigured (no-op); contributing (future…
error-handling
Consistent error handling across frontend and backend layers. TRIGGER when: implementing error boundaries, exception handlers, or try/catch blocks. SKIP: shaping HTTP error response bodies (use api-design); logging the error (use logging-standards). (Examples in React + Python.).
python-patterns
Python backend patterns: layered architecture, async I/O, dependency injection, repository/service separation. TRIGGER when: creating routes, models, schemas, or services in a Python backend. SKIP: REST contract design (use api-design); schema/index tuning (use database-optimization). (Examples: FastAPI + SQLAlchemy +…
api-design
RESTful API design standards: resource naming, HTTP methods, status codes, pagination, versioning. TRIGGER when: designing new API endpoints, defining error response shapes, or adding pagination/filtering. SKIP: implementing FastAPI route code (use python-patterns); error-handling internals (use error-handling).
qauthtrailingslash
Audit API routes for the trailing-slash / 307-redirect auth bug — where a missing or extra trailing slash makes the server issue an HTTP 307 redirect and the client silently drops the Authorization header, causing intermittent 401s. Use when reviewing or debugging FastAPI/Starlette (or similar) routes, auth-token loss…
turnstile-systematic-debugger
Debugging methodology -- reproduce, gather evidence, hypothesize, root-cause, fix, verify -- works on any bug report. Dispatched by /turnstile:systematic-debugger or conversate routing only.