windows-commands

windows-commands is a cursor rule for Cursor from SeloSlav/2d-multiplayer-survival-mmorpg. It costs 9 tokens per session (308 once invoked), scanned A, original, Apache-2.0.

A set of rules for writing terminal commands for Windows PowerShell, a command-line shell included with Windows. It maps common search, file-reading, counting, and command-discovery tasks to PowerShell commands.

In plain words
What is it for?
Use it when searching source files or logs, reading files, counting matches, locating installed commands, or writing other local terminal instructions for PowerShell.
Why use it?
Commands written for Unix shells may not work in PowerShell. These rules help developers use copy-pasteable commands that fit the project's Windows environment.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when searching source files or logs, reading files, counting matches, locating installed commands, or writing other local terminal instructions for PowerShell.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/seloslav/2d-multiplayer-survival-mmorpg/windows-commands
Install

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.

Clone the repo
git clone --depth 1 https://github.com/SeloSlav/2d-multiplayer-survival-mmorpg

Made for: Cursor.

Wrote 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.

agentmods badge for windows-commands

README.md
[![agentmods](https://agentmods.dev/badge/rules/seloslav/2d-multiplayer-survival-mmorpg/windows-commands.svg)](https://agentmods.dev/rules/seloslav/2d-multiplayer-survival-mmorpg/windows-commands)
Your own site
<a href="https://agentmods.dev/rules/seloslav/2d-multiplayer-survival-mmorpg/windows-commands"><img src="https://agentmods.dev/badge/rules/seloslav/2d-multiplayer-survival-mmorpg/windows-commands.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 308 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00308
Opus 5 $0.00005 $0.00154
Sonnet 5 $0.00002 $0.00062
Haiku 4.5 $0.00001 $0.00031

Measured 8d ago against content hash 8099b9c64569, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

windows-commands 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 8d 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.

.cursor/rules/windows-commands.mdc · 39 lines

What it actually says

Windows Command Compatibility Rules

This workspace runs on Windows (PowerShell). Use Windows-compatible command patterns when suggesting or running terminal commands.

Use These

  • Select-String instead of grep
  • Get-ChildItem instead of find
  • Get-Content instead of cat
  • Select-Object -First/-Last instead of head/tail
  • Measure-Object instead of wc
  • Get-Command / where.exe instead of which

Avoid These (Unix-only by default)

grep, sed, awk, cut, head, tail, wc, find, which, sudo, chmod, touch.

Project-Specific Examples

# Logs search
spacetime logs broth-bullets-local | Select-String -Pattern "cairn" -CaseSensitive:$false

# Rust source search
Get-ChildItem -Recurse -Filter "*.rs" | Select-String -Pattern "GrassAppearanceType"

# Count matching log lines
(spacetime logs broth-bullets-local | Select-String -Pattern "error" -CaseSensitive:$false).Count

Notes

  • Forward slashes in paths usually work, but prefer PowerShell-friendly quoting.
  • Keep commands copy-paste friendly for PowerShell users.
Changes

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.

  1. 8d ago First seen · 39 lines · 9 tokens per session scan A 8099b9c64569

Subscribe to this mod's changes

windows-commands is a cursor rule published in the GitHub repository SeloSlav/2d-multiplayer-survival-mmorpg (177 stars, last pushed 19d ago), licensed Apache-2.0. It adds 9 tokens to every session and 308 once invoked, about $0.0000 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-30.