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 skills add EliasOulkadi/shokunin --skill whendone-plusgit clone --depth 1 https://github.com/EliasOulkadi/shokuninWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/eliasoulkadi/shokunin/whendone-plus)<a href="https://agentmods.dev/skills/eliasoulkadi/shokunin/whendone-plus"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/whendone-plus/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/eliasoulkadi/shokunin/whendone-plus"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/whendone-plus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 48 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.1 | $0.00116 | $0.01618 |
| Opus 5.5 | $0.00046 | $0.00647 |
| Sonnet 5.5 | $0.00023 | $0.00324 |
| Haiku 4.5 | $0.00012 | $0.00162 |
Grade A, and why
whendone-plus 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WhenDone Plus
Automatically notify when long-running commands complete.
How It Works
- User runs a long command (e.g.
npm test,docker build,git push) - The agent monitors the command execution time
- If the command runs longer than the threshold (default 10s), the agent notifies the user on completion
- Exit code is passed through
Workflow
Step 1: Detect long-running command
Identify commands likely to exceed threshold:
npm test,npm run test,npx playwright testdocker build,docker compose up,docker compose downgit push,git pull,git clonepip install,npm install,pnpm install,yarn installcargo build,cargo test,go build,dotnet build- Custom scripts, database migrations, data processing pipelines
ffmpeg,rsync,scp, large file transfers
Step 2: Monitor execution
Start a background timer when the command begins. Track:
- Elapsed wall-clock time
- Peak memory usage (if available)
- Child process tree (for pipeline awareness)
Step 3: Notify on completion
Basic notification format:
✅ "Command finished: npm test completed in 142s (exit 0)"
❌ "Command finished: docker build failed in 89s (exit 1)"
Include:
- Command name (first word + key args)
- Execution time (rounded to seconds)
- Exit code (success/failure)
- Optional: memory peak, output file path if redirected
Step 4: Handle edge cases
- Commands completing under 10s: no notification (too fast to matter)
- Interactive/TUI commands (vim, nano, htop): skip (user is watching)
- Piped commands (e.g.
npm test | grep error): monitor the pipeline, not the first process - Backgrounded commands (
&): notify on background process completion - Chained commands (
;): notify per-segment or in aggregate - Commands killed by signal: notify with signal name (e.g. "killed by SIGTERM")
Notification Mechanisms
Windows Toast Notification (PowerShell)
Add-Type -AssemblyName System.Windows.Forms
$balloon = New-Object System.Windows.Forms.NotifyIcon
$balloon.Icon = [System.Drawing.SystemIcons]::Information
$balloon.BalloonTipTitle = "Command Complete"
$balloon.BalloonTipText = "npm test finished in 142s (exit 0)"
$balloon.Visible = $true
$balloon.ShowBalloonTip(5000)
Start-Sleep -Seconds 5
$balloon.Dispose()
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 180 lines · 116 tokens per session scan A d5a1db5d1e5c
whendone-plus is a skill published in the GitHub repository EliasOulkadi/shokunin (112 stars, last pushed 22d ago), licensed MIT. It adds 116 tokens to every session and 1,618 once invoked, about $0.0005 per session on Opus 5.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-09-03.
Other skills, from other repositories
ask-user-questions
Ask clarifying questions to users via interactive TUI. Use when you need user input on preferences, implementation choices, or ambiguous instructions.
cleanup-discipline
Disciplined disk-cleanup workflow for reclaiming storage without destroying live runtimes, unpushed work, or unrecoverable data. Use for ANY disk-space cleanup, storage reclamation, "what can we delete", purge/prune campaigns, or when asked to free up space — survey, classify, verify, capture, delete, report.
refit
Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user approval.
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
externalize-operator
MUST READ before calling externalizeop or saveexternalization. Required workflow steps.
cmux-customization
Customize cmux for an end user, including terminal, browser, Markdown, diff, file preview, notes, HTML, and right-sidebar viewers. Use when changing cmux.json actions, custom commands, workspace layouts, plus-button behavior, surface tab bar buttons, Command Palette entries, Dock controls, sidebar and app settings…