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/ussdeveloper/memory-starWrote 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/ussdeveloper/memory-star/rebuild-installer)<a href="https://agentmods.dev/rules/ussdeveloper/memory-star/rebuild-installer"><img src="https://agentmods.dev/badge/rules/ussdeveloper/memory-star/rebuild-installer/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/rules/ussdeveloper/memory-star/rebuild-installer"><img src="https://agentmods.dev/badge/rules/ussdeveloper/memory-star/rebuild-installer.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.00517 | $0.00517 |
| Opus 5.5 | $0.00207 | $0.00207 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
rebuild-installer 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.
What it actually says
Rebuild the installer after changes
When you change any file that is part of what the installer ships or installs, you MUST rebuild the installer afterwards so the EXE/zip stay in sync with source.
Trigger files
Rebuild if you edit any of these (or their copies under dist/):
dist/MemoryStar-Setup.ps1,dist/MemoryStar-Setup.bat,dist/setup_launcher.pyserver.py,database.py,config.py,quantum_storage.py,ui.html,requirements.txt- anything under
dist/install/orextension/
How to rebuild
powershell -ExecutionPolicy Bypass -File "<repo>\dist\build.ps1"
This re-syncs the dist/memorystar payload, repackages the VSIX, and rebuilds the
installer. build.ps1 reads $script:InstallerVersion from MemoryStar-Setup.ps1
and names artifacts accordingly.
Artifact naming (always versioned)
Every build MUST produce version-stamped artifacts so downloads are self-identifying:
MemoryStar-Setup-v<version>.exe(canonical installer — always written)MemoryStar-Windows-v<version>.zip(canonical package — always written)MemoryStar-Setup.exe/MemoryStar-Windows.zipare unversioned aliases, refreshed best-effort (skipped with a warning if locked by a running process).
When pointing the user to the installer, refer them to the versioned file
(MemoryStar-Setup-v<version>.exe), not the alias.
Rules
- Bump
$script:InstallerVersioninMemoryStar-Setup.ps1AND update the header comment# ... vX.Y.Z, then add aCHANGELOG.mdentry when behavior changes. - Keep
MemoryStar-Setup.ps1ASCII-only (non-ASCII breaks PowerShell on some Windows locales;build.ps1fails fast on this) and syntactically valid (build.ps1runs an AST parse check before building). - After building, confirm the versioned EXE timestamp/size so the rebuild actually succeeded.
- Don't tell the user the installer is "built" unless
build.ps1finished successfully.
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 · 51 lines · 517 tokens per session scan A 3684d311d016
rebuild-installer is a cursor rule published in the GitHub repository ussdeveloper/memory-star (0 stars, last pushed 3mo ago), licensed MIT. It adds 517 tokens to every session, about $0.0021 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 cursor rules, from other repositories
nativescript
NativeScript best practices and patterns for mobile applications.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.