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 skills/edison-watch/custom-mcps/waitnpx skills add Edison-Watch/Custom-MCPs --skill waitgit clone --depth 1 https://github.com/Edison-Watch/Custom-MCPsWhat 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.00022 | $0.00354 |
| Opus 5 | $0.00011 | $0.00177 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
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 yesterday.
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.
This is a copy
100% identical to wait — 0 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.
What it actually says
Wait Skill
Use this skill whenever the user asks the assistant to pause or wait for a few minutes during a task. Instead of issuing a single long sleep command (which often hits the 2-minute shell timeout), run one-minute sleeps repeatedly for the requested duration.
Workflow
-
Determine the wait time. Parse the user’s request for a duration expressed in minutes. If the request is vague, ask a clarifying question (e.g., “How many minutes should I wait?”) before running commands.
-
Enforce sane limits. If the user requests a very large number of minutes, warn them and offer to break the wait into smaller chunks or confirm before proceeding.
-
Execute sequential Bash sleeps. For each of the requested N minutes, issue a separate
bashtool call withsleep 60. Before each call, report the upcoming iteration asexecuting sleep: i/N: bash sleep 60so observers know how many sleeps will run. Avoid bundling the sleeps into a single script; the goal is to keep every sleeping command under the 2-minute timeout. -
Report completion. Once the loop finishes, notify the user that the wait is over and resume the primary task.
Error handling
- If the shell command fails (e.g.,
sleepunavailable), report the failure and stop waiting. - If the user changes their mind mid-wait, cancel the remaining iterations and explain how much time was actually spent waiting.
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.
- yesterday First seen · 26 lines · 22 tokens per session scan A cd372da054b2
wait is a skill published in the GitHub repository Edison-Watch/Custom-MCPs (0 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 354 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to wait, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…