A command for planning or starting a group of locally run Spring Boot services. Spring Boot is a framework for building Java applications, and the command can use Docker Compose or the project's Gradle or Maven launcher.

Use it to preview or launch all services, or one named service, from a fleet configuration. It also records the commands, working folders, and log paths.

Starting several services by hand is repetitive and can leave their output in places that are hard to inspect. This command creates a plan and can save each service's output to log files.

run — 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/run

Clone the repo

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

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

When invoked 461 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.00027	$0.00461
Opus 5	$0.00014	$0.00230
Sonnet 5	$0.00005	$0.00092
Haiku 4.5	$0.00003	$0.00046

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

Security

Grade A, and why

run 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/run.md · 38 lines

What it actually says

Plan or launch the Spring Boot fleet locally.

Input: $ARGUMENTS — optional bare service name (default: all), plus optional --execute to actually start the processes (default: print the plan only).

Per-service resolution (from services[].stack produced by /fleet-init):

dockerCompose=true → docker compose up -d in the repo (Spring Boot Docker Compose support discovers compose.yaml and wires @ServiceConnection beans automatically — the modern local-dev default).
otherwise → gradle bootRun or mvn spring-boot:run, with stdout/stderr tee'd to <logDir>/<service>.log so /debug and /logs work without any logback changes.

Steps:

Locate spring-fleet.config.json (cwd, else suggest /fleet-init).
Plan first (no --execute):
```
python "${CLAUDE_PLUGIN_ROOT}/scripts/run_fleet.py" --config ./spring-fleet.config.json [--service NAME]
```
Show the JSON plan. Each entry has: service, cwd, mode (compose / gradle / maven), command, logPath, and tee (whether stdout will be redirected).
Confirm with the user before executing — launching processes is not reversible and may bind to fleet ports already in use.
Execute with --execute when the user approves:
```
python "${CLAUDE_PLUGIN_ROOT}/scripts/run_fleet.py" --config ./spring-fleet.config.json --execute [--service NAME]
```
Each spawned process is detached. Stop them with the usual OS tools (or docker compose down for compose-managed services).
After launch, suggest /logs --follow (or tail_service_log MCP tool) to confirm services are healthy.

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 · 38 lines · 0 tokens per session scan A 699a9ecacc0e

Subscribe to this mod's changes

run is a command published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 461 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.

Containers DevOps and cloud claude-code claude-code-plugin claude-plugin developer-tools

design-to-code

Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…

yonatangross/orchestkit · 86 tokens

run

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

design-to-code

dockerfile

deploy

brand-setup

save

graphify