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 windows-powershellgit 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/windows-powershell)<a href="https://agentmods.dev/skills/eliasoulkadi/shokunin/windows-powershell"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/windows-powershell/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/windows-powershell"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/windows-powershell.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 Rogue Agent · line 190 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00098 | $0.02410 |
| Opus 5.5 | $0.00039 | $0.00964 |
| Sonnet 5.5 | $0.00020 | $0.00482 |
| Haiku 4.5 | $0.00010 | $0.00241 |
Grade A, and why
windows-powershell 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Windows PowerShell
Windows 11 system administration and automation with PowerShell 7.
Workflow
Step 1: System health check
scripts/system-info.ps1
Outputs:
- OS: Windows 11 build, edition, install date
- CPU: Model, cores, current usage %
- RAM: Total, used, free, usage %
- Disk: Per drive: total, used, free, usage %
- Top 5 processes by memory usage
- Network: Adapters, IP addresses
- Uptime: Days since last restart
- Windows Updates: Pending update count
If RAM usage > 80% or disk usage > 90%: proceed to Step 2.
Step 2: System cleanup
# Preview what would be cleaned
scripts/cleanup-system.ps1 -DryRun
# Clean everything
scripts/cleanup-system.ps1
Cleans:
- Windows temporary files
- Recycle Bin
- Windows Update cache
- npm/yarn/pnpm cache
- Docker unused data
- Windows.old (if present)
- Prefetch files
Reports total space recovered.
Step 3: Install development tools
# Install everything
scripts/install-tools.ps1
# Install specific categories only
scripts/install-tools.ps1 -Scope dev # Git, Node, Python, VS Code
scripts/install-tools.ps1 -Scope tools # 7-Zip, Windows Terminal, Oh My Posh
The script checks if each tool is already installed before attempting. Uses winget as primary, falls back to scoop.
Step 4: Set up PowerShell profile
Copy the premium profile template:
# Install the premium profile
Copy-Item "~\\.config\\opencode\\skills\\windows-powershell\\assets\\Microsoft.PowerShell_profile.ps1" $PROFILE
# Reload profile
. $PROFILE
The profile includes:
- Oh My Posh prompt with git status
- PSReadLine with autocomplete and syntax highlighting
- Git aliases:
gst(status),ga(add),gc(commit),gp(push),gl(pull),gb(branch) - npm aliases:
ni(install),nrd(run dev),nrb(run build),nt(test) - Docker aliases:
dps(ps),dlog(logs),dstop(stop),drm(rm) - Utils:
touch,which,ll(ls -la),mkcd(mkdir + cd),admin(runas admin)
What ships with it
5 files 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 · 290 lines · 98 tokens per session scan A 90137491a542
windows-powershell is a skill published in the GitHub repository EliasOulkadi/shokunin (112 stars, last pushed 27d ago), licensed MIT. It adds 98 tokens to every session and 2,410 once invoked, about $0.0004 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.
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.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
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.
getting-started
Connect Taskade and show the user what they can do with it. Use when the user says "set up Taskade", "connect Taskade", "what can you do in Taskade", "what is in my Taskade workspace", or when a Taskade tool fails with a sign-in or plan error.