stop

stop is a command for coding agents from tinhtran24/maestro. It costs 0 tokens per session (113 once invoked), scanned A, a copy of stop, Apache-2.0.

A command that stops the Maestro background service and waits for it to shut down.

In plain words
What is it for?
Use it to stop Maestro normally, choose a longer shutdown timeout, or return the result as JSON.
Why use it?
It provides a controlled way to end the service and lets you extend the waiting time if shutdown is slow.

Command

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/tinhtran24/maestro/stop
Clone the repo
git clone --depth 1 https://github.com/tinhtran24/maestro
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 113 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00113
Opus 5 $0.00000 $0.00056
Sonnet 5 $0.00000 $0.00023
Haiku 4.5 $0.00000 $0.00011

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

Security

Grade A, and why

stop 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 3d 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.

Origin

This is a copy

89% identical to stop — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

backend/internal/skillassets/using-maestro/commands/stop.md · 29 lines

What it actually says

to stop

Stop the Maestro daemon.

Syntax

maestro stop [flags]

Flags

Flag Meaning Default / Required
--json Output stop result as JSON -
--timeout duration How long to wait for daemon shutdown 10s

Examples

# Stop the daemon
maestro stop
# Stop with a longer timeout
maestro stop --timeout 30s
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.

  1. 3d ago First seen · 29 lines · 0 tokens per session scan A 3cfde315f110

Subscribe to this mod's changes

stop is a command published in the GitHub repository tinhtran24/maestro (3 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 113 tokens. A static security scan graded it A with 0 findings. It is 89% identical to stop, differing in 10 lines, and is treated as a copy.