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 commands/1mcp-app/agent/waitgit clone --depth 1 https://github.com/1mcp-app/agentWhat 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.00015 | $0.00359 |
| Opus 5 | $0.00008 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
wait 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.
What it actually says
Wait Command
Wait for enabled configured static MCP servers to become connected and available through the authenticated /api/v1/inspect status contract.
npx -y @1mcp/agent wait [server] [options]
Without a server, wait covers all matching configured static servers. Templates and disabled servers are excluded. A template target returns server_not_load_tracked; an unknown target returns server_not_found.
Options
[server]- One configured static server to wait for--timeout <ms>- Positive timeout in milliseconds, default30000--url, -u <url>- Override the auto-detected runtime URL--context <name>- Use a named Runtime Target Context--preset,--tag-filter,--tags- Apply the same client-facing filters asinspect--format <toon|text|json>- Select success output format
Behavior
Success requires every requested server to report connected and available. failed, cancelled, awaiting_oauth, and unavailable terminal states stop immediately with a structured nonzero error. A timeout includes the last observed states and a recovery command. Waiting never cancels background loading.
Use wait before run when a script must depend on a newly started backend. run also checks inspect status before its REST-to-MCP fallback and returns server_loading with the same recovery command when the backend is still loading.
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 · 30 lines · 15 tokens per session scan A 35d5801797d2
wait is a command published in the GitHub repository 1mcp-app/agent (494 stars, last pushed 3d ago), licensed Apache-2.0. It adds 15 tokens to every session and 359 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-30.
Other commands, from other repositories
go
MCP tool management and workflow proxy.
strict-development-rules
These rules apply strictly to all code modifications and additions within the Gemini CLI project.
release-harn
Run the tag-first Harn release workflow.
harn-release
Run the tag-first Harn release workflow.
web-component
Create a new web component following the established project conventions.
send
Send a WhatsApp message using the wu MCP server.