A command that scans a directory containing multiple code repositories and creates or updates a fleet configuration file. The file records build tools, services, shared libraries, ports, request-tracing keys, and service dependencies.

Use it to prepare a group of repositories for shared service debugging and log analysis, including repositories described by Backstage catalog files.

It removes the manual work of documenting how several repositories fit together. It also checks that the resulting configuration has the required fields and types.

fleet-init — Command by talayash

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.

agentmods

npx agentmods add commands/talayash/spring-fleet/fleet-init

Clone the repo

git clone --depth 1 https://github.com/talayash/spring-fleet

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 412 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00019	$0.00412
Opus 5	$0.00010	$0.00206
Sonnet 5	$0.00004	$0.00082
Haiku 4.5	$0.00002	$0.00041

Measured 2d ago against content hash 9288d24567f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fleet-init 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.

commands/fleet-init.md · 35 lines

What it actually says

Initialize or refresh the fleet config.

Input: $ARGUMENTS — optional repos root path. If omitted, ask the user (or use an existing config's reposRoot).

Steps:

Determine the repos root. Confirm it exists.
Run the scanner to produce a draft:
```
python "${CLAUDE_PLUGIN_ROOT}/scripts/scan_repos.py" --root <reposRoot>
```
It detects build tool, services vs shared libs, ports, and context paths.
The draft pre-fills traceKeys with the modern OTel-first default (trace_id, span_id, sessionId, requestId) and seeds topology from any Backstage catalog-info.yaml files it finds at repo roots (each dependsOn: component:* becomes a [from, to] edge; components with no inbound dependency become entries). Ask the user to confirm:
- traceKeys: which MDC keys actually identify a request/session in their fleet (drop entries that are never emitted).
- topology: confirm or amend the Backstage-derived entries and edges; for fleets without Backstage, fill these in manually. Pre-fill from any existing spring-fleet.config.json if present.
Validate the result against ${CLAUDE_PLUGIN_ROOT}/spring-fleet.config.schema.json (required fields, types).
Write spring-fleet.config.json to the user's project root. Remind them it is .gitignored and must never be committed.
If logs are console-only or scattered, suggest the spring-fleet-logging-setup skill so /debug has stable per-service logs.

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.

2d ago First seen · 35 lines · 19 tokens per session scan A 9288d24567f8

Subscribe to this mod's changes

fleet-init is a command published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 412 once invoked, about $0.0001 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.

Debugging Languages claude-code claude-code-plugin claude-plugin developer-tools

fleet-init

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

seo-drift

brand-setup

save

ros-first-dollar

graphify

screens