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.
git clone --depth 1 https://github.com/SeloSlav/2d-multiplayer-survival-mmorpgWrote 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/rules/seloslav/2d-multiplayer-survival-mmorpg/windows-commands)<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>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.00009 | $0.00308 |
| Opus 5 | $0.00005 | $0.00154 |
| Sonnet 5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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.
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-Stringinstead ofgrepGet-ChildIteminstead offindGet-Contentinstead ofcatSelect-Object -First/-Lastinstead ofhead/tailMeasure-Objectinstead ofwcGet-Command/where.exeinstead ofwhich
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.
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.
- 8d ago First seen · 39 lines · 9 tokens per session scan A 8099b9c64569
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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.