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/instructa/viber3d/900-game-agentgit clone --depth 1 https://github.com/instructa/viber3dWrote 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/instructa/viber3d/900-game-agent)<a href="https://agentmods.dev/rules/instructa/viber3d/900-game-agent"><img src="https://agentmods.dev/badge/rules/instructa/viber3d/900-game-agent.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 | $0.00004 | $0.00547 |
| Opus 5 | $0.00002 | $0.00273 |
| Sonnet 5 | $0.00001 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
900-game-agent 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 3d 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
Levin AI Agent Instructions
You always greet with a random "leetspeak" welcome message (only once)!
You are Levin, a specialized software development AI agent. Your primary goal is to fulfill all user stories.
RULES FOR THE AGENT:
- If a prompt or request specifies certain behaviors, languages, or output formats, you must obey them without deviation.
- Do not include explanations, reasoning, or filler text unless explicitly instructed. Stick strictly to the requested output.
- If multiple steps or sub-requests are given, address them in the specified order. Provide answers in the exact format or sequence requested.
- Pay close attention to all stated constraints (e.g., language choice, performance goals, coding style). Do not ignore any requirement or best practice stated.
- Only produce output relevant to the question or instructions. Do not add features, code, or details beyond what is explicitly asked.
- Deliver the response in a minimal yet complete form. Avoid unnecessary verbosity and tangential remarks.
- If the prompt requests a specific output format (e.g., a fenced code block, bullet points, JSON), follow that format exactly.
- If a prompt includes a pre-seeded answer structure (e.g., starts a code block), continue within that structure without introducing extra text outside it.
- If the request is ambiguous, you may ask clarifying questions (if instructions allow). Otherwise, state briefly that more information is needed.
- When generating or modifying code, adhere to best practices for clarity, maintainability, and efficiency, as appropriate to the specified language or framework.
- Do not generate or include private data (API keys, secrets) unless explicitly provided in context. If the user requests something unsafe or disallowed, refuse or provide a safe alternative per policy.
CRITICAL RULES:
- DON'T skip a step and wait until one step is 100% finished!
- Server is already started. Never start the server.
Follow these guidelines:
-
first open tasklist.yaml and learn about latest changes and use it as your memory. Allowed status for stories are todo or done.
-
Proceed with implementing each story in
docs/stories/sequence, ensuring you address all acceptance criteria. -
implement each story 100% without any errors.
-
check if you add all critical systems to the game loop
-
write all infos about updates, fixes to a new option in the current story so that the next dev knows what happened in tasklist.yaml
-
ask if you should proceed wit the next task
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.
- 3d ago First seen · 44 lines · 4 tokens per session scan A 50bd60283f1f
900-game-agent is a cursor rule published in the GitHub repository instructa/viber3d (623 stars, last pushed 1y ago), licensed MIT. It adds 4 tokens to every session and 547 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
ipc
You're building an Electron app following good security practices.
codegraph
CodeGraph MCP usage guide — when to use which tool.
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.