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/glavin001/vibe-land-old/techguidegit clone --depth 1 https://github.com/Glavin001/vibe-land-oldWhat 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.04512 | $0.04512 |
| Opus 5 | $0.02256 | $0.02256 |
| Sonnet 5 | $0.00902 | $0.00902 |
| Haiku 4.5 | $0.00451 | $0.00451 |
Grade C, and why
techguide scanned grade C with 2 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
* Install: `curl https://sh.rustup.rs -sSf | sh` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
* Install: `curl https://sh.rustup.rs -sSf | sh` This is a copy
100% identical to techguide — 8 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Coding Starter Pack: 3D Multiplayer - Technical Guide
This document describes the architecture, setup, workflow, and key development patterns for the Vibe Coding Starter Pack 3D Multiplayer project. SpacetimeDB v2.0.1 is used throughout.
1. Project Overview
- Goal: Provide a foundation for building 3D multiplayer web games using SpacetimeDB as the backend.
- Backend: SpacetimeDB module written in Rust (
server/). Handles game logic, state management, and data persistence. Compiled to WASM. - Frontend: Client application built with Vite, React 19, TypeScript, and React Three Fiber (
client/). Connects to SpacetimeDB via WebSocket, subscribes to data, calls reducers, and renders the game state.
2. Game Architecture
The starter pack uses a modular, component-based architecture with the following core systems:
- Core Game Loop: Managed in
client/src/App.tsx, which initializes all components and runs the input send cycle at 20Hz - Rendering System: Handled by Three.js via React Three Fiber with scene setup in
client/src/components/GameScene.tsx - Character System: Player controls, FBX model loading, animations, and client-side prediction in
client/src/components/Player.tsx - UI System: HUD elements and feedback in
client/src/components/PlayerUI.tsxandclient/src/components/DebugPanel.tsx - Multiplayer System: Client-server communication in
client/src/App.tsxand server-side code inserver/src/directory - Load Testing: Bot simulation in
client/src/simulation.tsfor stress-testing with configurable bot count
3. Core SpacetimeDB v2 Concepts
- Tables: Relational data storage defined as Rust structs with
#[spacetimedb::table]. Key tables includeplayerandlogged_out_player. Tables must be markedpublicfor client access. Thename = "..."attribute defines the SQL table name; theaccessor = "..."attribute defines the Rust accessor name used inctx.db. Table names in client SQL subscriptions are case-sensitive (e.g.,name = "player"requiresSELECT * FROM player). - Reducers: Atomic, transactional Rust functions (
#[spacetimedb::reducer]) that modify table state. Triggered by client calls or internal events. Key reducers:register_player,update_player_input, lifecycle reducers (identity_connected,identity_disconnected). - Subscriptions: Clients subscribe to SQL queries (e.g.,
SELECT * FROM player) usingconn.subscriptionBuilder(). IMPORTANT: Register.onApplied()and.onError()callbacks before calling.subscribe()— in v2, backfill data fires immediately on subscribe. - Generated Bindings: The
spacetime generatecommand creates TypeScript code (client/src/generated/) based on the Rust module's schema, providing type-safe access to tables, reducers, and types on the client. Types are ingenerated/types.ts. - Identity: Represents a unique, authenticated user. In v2 reducers:
ctx.sender()(method call with parentheses). On client:conn.identity. Used as the primary key for player-related tables.
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.
- 2d ago First seen · 302 lines · 4,512 tokens per session scan C d7d3e54695e0
techguide is a cursor rule published in the GitHub repository Glavin001/vibe-land-old (3 stars, last pushed 4mo ago), licensed MIT. It adds 4,512 tokens to every session, about $0.0226 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 100% identical to techguide, differing in 8 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation patterns.