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/phuonghx/aim-cli/powershell-windowsnpx skills add phuonghx/aim-cli --skill powershell-windowsgit clone --depth 1 https://github.com/phuonghx/aim-cliWhat 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.00083 | $0.01145 |
| Opus 5 | $0.00042 | $0.00573 |
| Sonnet 5 | $0.00017 | $0.00229 |
| Haiku 4.5 | $0.00008 | $0.00114 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell on Windows
PowerShell has a handful of sharp edges that bite predictably. The rules below are not stylistic preferences -- ignoring them produces parser errors or silent wrong behavior.
Group cmdlet calls inside conditions
When a cmdlet result feeds a logical operator, wrap the call in parentheses. The parser otherwise treats -or/-and as a parameter to the cmdlet.
# Breaks: -or is read as an argument to Test-Path
if (Test-Path $a -or Test-Path $b) { ... }
# Works: each call is its own grouped expression
if ((Test-Path $a) -or (Test-Path $b)) { ... }
# Same rule with a comparison on one side
if ((Get-Item $p) -and ($count -eq 5)) { ... }
Stick to ASCII in script output
Non-ASCII glyphs (emoji, check marks, box drawing) cause "Unexpected token" errors on many Windows consoles and code pages. Use bracketed ASCII tags instead.
| Meaning | Avoid | Use |
|---|---|---|
| Success | check / tick marks | [OK] [+] |
| Failure | cross / red circle | [X] [!] |
| Warning | warning sign | [WARN] [*] |
| Info | info symbol | [INFO] [i] |
| In progress | hourglass | [...] |
Guard against null before dereferencing
Touching a property or method on $null throws -- and under Set-StrictMode even reading an unset variable does. Check first.
# Risky
if ($items.Count -gt 0) { ... }
$len = $name.Length
# Safe
if ($items -and $items.Count -gt 0) { ... }
if ($name) { $len = $name.Length }
Pull deep expressions out of strings
Interpolating a multi-hop property chain inside a string is fragile. Assign it to a variable, then interpolate the variable.
# Fragile
Write-Output "City: $($order.customer.address.city)"
# Clear
$city = $order.customer.address.city
Write-Output "City: $city"
Choose the right error preference
$ErrorActionPreference sets how non-terminating errors behave:
| Value | Fits |
|---|---|
Stop |
development -- fail loudly and early |
Continue |
production scripts that should push through |
SilentlyContinue |
spots where an error is expected and fine |
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 · 139 lines · 83 tokens per session scan A d7e7ad9200e2
powershell-windows is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 1,145 once invoked, about $0.0004 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-31.
Other skills, from other repositories
hs-release
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
hindsight-local
Store user preferences, learnings from tasks, and procedure outcomes. Use to remember what works and recall context before new tasks. (user).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
user-persona
Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use empathy-map; for motivation framing use jobs-to-be-done.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).