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/savagelysubtle/BIG-BRAIN-Memory-BankWrote 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/savagelysubtle/big-brain-memory-bank/platform-awareness)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/platform-awareness"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/platform-awareness.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.01119 | $0.01119 |
| Opus 5 | $0.00560 | $0.00560 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade C, and why
platform-awareness scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| Delete directory | rmdir /s /q dir | rm -rf dir | This is a copy
100% identical to platform-awareness — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PLATFORM AWARENESS
TL;DR: Always identify the operating system at the beginning of a task. Prefer built-in tools over platform-specific commands when available. When terminal commands are necessary, adapt them according to the platform.
🔧 TOOLS-FIRST APPROACH
Use these built-in tools as your first choice:
list_dir- For listing directory contents (instead of dir/ls)edit_file- For creating/editing files (instead of echo/touch)read_file- For examining file contents- Use relative paths directly with tools (no cd needed)
run_terminal_cmd- For terminal commands (ONE AT A TIME)
🖥️ PLATFORM IDENTIFICATION
At the INITIALIZATION phase of every task, identify the platform:
### Platform Detection
Current environment: [Windows/Mac/Linux]
Path separator: [\ or /]
🚨 KEY PLATFORM DIFFERENCES
| Operation | Windows | Mac/Linux |
|---|---|---|
| Path separator | \ (backslash) | / (forward slash) |
| Create empty file | echo.> filename.txt | touch filename.txt |
| Create nested dirs | Create one by one | mkdir -p path/to/dir |
| List directory | dir | ls |
| Check if dir exists | if exist dir\NUL | if [ -d dir ] |
| Check if file exists | if exist file.txt | if [ -f file.txt ] |
| Delete file | del file.txt | rm file.txt |
| Delete directory | rmdir /s /q dir | rm -rf dir |
📦 WEB DEVELOPMENT WORKFLOW
For modern web development environments like Vite/React:
NPM Commands (Safe across platforms)
# Installing dependencies
npm install # Install all dependencies from package.json
npm install react # Install a single package
npm install react react-dom # Install multiple packages at once
# Running scripts
npm run dev # Start development server
npm run build # Build for production
npm run test # Run tests
# Creating projects
npm create vite@latest my-app -- --template react
Vite Development (Safe across platforms)
# Starting dev server
cd project-directory
npm run dev
# Building
npm run build
# Previewing build
npm run preview
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.
- 6d ago First seen · 175 lines · 1,119 tokens per session scan C 8472277b8753
platform-awareness is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It adds 1,119 tokens to every session, about $0.0056 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to platform-awareness, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
composer-core
Always-on builder spine — continue the app, demoable slice, Build loop, Run/Wired handoff, ask only on high confusion weight.
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
composer-reasoning
High-stakes judgment for architectural or multi-option work — tradeoffs, one-way doors, reason-then-re-evaluate, honest pushback.
composer-debugging
Root-cause debugging — reproduce, trace data flow, test cheapest hypothesis, fix the cause not the symptom.
composer-deep-research
Edge-case research for audits, vendor comparisons, and unfamiliar APIs — primaries first, iterative retrieval, explicit conflicts; not the default build path.