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 rules/peltmonger/stardrive/cursorrulesgit clone --depth 1 https://github.com/peltmonger/stardriveWhat 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.00316 | $0.00316 |
| Opus 5 | $0.00158 | $0.00158 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
cursorrules 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.
What it actually says
🛑 CRITICAL: REPOSITORY BOOTSTRAP DIRECTIVE 🛑
As an AI agent operating in this repository, you MUST execute the following state check before analyzing, coding, or responding to any user prompt:
- CHECK STATE: Silently verify if the file
STARDRIVE_AGENT_MODE.mdexists in the root directory. - IF MISSING (UNINITIALIZED):
- Intercept the prompt: Acknowledge to the user that you are running the initial repository setup first.
- Never (!) proceed without this file being present!
- Read the file
SETUP.mdin the./.ai/directory.. - Execute ALL setup, scaffolding, and configuration instructions defined in
SETUP.mdand related files. Ask the user about clarification where necessary. - Create the
STARDRIVE_AGENT_MODE.mdfile in the root directory to mark initialization as complete, setting its content to "project" or "boilerplate" - depending on what the user's case is about. - Proceed to fulfill the user's original request.
- IF PRESENT (INITIALIZED):
- Directly proceed to fulfilling the user's prompt.
- Mind the content of the
STARDRIVE_AGENT_MODE.mdas it defines your general scope as described in theAGENTS.md.
Additionally, always mind the guidelines in AGENTS.md!
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 · 16 lines · 316 tokens per session scan A 67ee11ce9703
cursorrules is a cursor rule published in the GitHub repository peltmonger/stardrive (183 stars, last pushed 2d ago), licensed MIT. It adds 316 tokens to every session, about $0.0016 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
markdy-syntax
Always follow MarkdyScript syntax rules when generating or editing .markdy and .mdy architecture diagrams.
nextjs-standards
Cursor rule "nextjs-standards" from solana-foundation/solana-com, covering authoritative guidelines, code style, file & folder conventions, rendering strategy and state & data.
astro-strapi-loader
Strapi 5 + @sensinum/astro-strapi-loader — content.config.ts, populate, qs, locales.
react-components
Rules for writing React components in this project.
server-patterns
Rules for server-side Express code.
00-project-core
本项目通用约定（结构、语言、改动边界）.