Borrowing it
Nothing to install: this file belongs to MisonL/Ling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MisonL/Ling/main/.agents/skills/powershell-windows/SKILL.mdgit clone --depth 1 https://github.com/MisonL/LingWrote 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/misonl/ling/powershell-windows)<a href="https://agentmods.dev/skills/misonl/ling/powershell-windows"><img src="https://agentmods.dev/badge/skills/misonl/ling/powershell-windows/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/misonl/ling/powershell-windows"><img src="https://agentmods.dev/badge/skills/misonl/ling/powershell-windows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.01347 |
| Opus 5.5 | $0.00016 | $0.00539 |
| Sonnet 5.5 | $0.00008 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
powershell-windows 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Windows 实践模式
针对 Windows PowerShell 的核心模式与关键陷阱。
1. 运算符语法规则
关键：必须使用圆括号（Parentheses）
| [FAIL] 错误做法 | [OK] 正确做法 |
|---|---|
if (Test-Path "a" -or Test-Path "b") |
if ((Test-Path "a") -or (Test-Path "b")) |
if (Get-Item $x -and $y -eq 5) |
if ((Get-Item $x) -and ($y -eq 5)) |
准则： 在使用逻辑运算符时，每一个 Cmdlet（命令）的调用必须封装在圆括号内。
2. Unicode（统一码）/Emoji（表情符号）限制
关键：脚本中严禁使用 Unicode
| 用途 | [FAIL] 禁止使用 | [OK] 推荐使用 |
|---|---|---|
| 成功 | [OK] OK | [OK] [+] |
| 错误 | [FAIL] X [CRITICAL] | [!] [X] |
| 警告 | [WARN] [SUGGESTION] | [*] [WARN] |
| 信息 | ℹ | [i] [INFO] |
| 进度 | ⏳ | [...] |
准则： 在 PowerShell 脚本中仅使用 ASCII（ASCII 码）字符。
3. 空值检查模式
在访问前始终检查
| [FAIL] 错误做法 | [OK] 正确做法 |
|---|---|
$array.Count -gt 0 |
$array -and $array.Count -gt 0 |
$text.Length |
if ($text) { $text.Length } |
4. 字符串内插（Interpolation）
复杂表达式的处理
推荐做法： 先存储到变量中，再进行内插。
$value = $obj.prop.sub
Write-Output "Value: $value"
5. 错误处理
ErrorActionPreference（错误处理偏好）配置
| 取值 | 使用场景 |
|---|---|
| Stop | 开发阶段（快速失败） |
| Continue | 生产环境脚本 |
| SilentlyContinue | 预期可能会发生错误时 |
Try/Catch（错误捕获）最佳实践
- 不要在 try 块内部直接返回。
- 始终使用 finally 块进行资源清理。
- 在 try/catch 结构之后再执行返回操作。
6. 文件路径处理
Windows 路径规则
| 模式 | 用途 |
|---|---|
| 字面量路径 | C:\Users\User\file.txt |
| 变量路径 | Join-Path $env:USERPROFILE "file.txt" |
| 相对路径 | Join-Path $ScriptDir "data" |
准则： 使用 Join-Path 以确保跨平台的路径安全性。
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 · 167 lines · 40 tokens per session scan A 3a64ef2371b5
powershell-windows is a skill published in the GitHub repository MisonL/Ling (8 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 1,347 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…