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 skills add nonlooped/roblox-suite --skill roblox-networkinggit clone --depth 1 https://github.com/nonlooped/roblox-suiteWrote 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/skills/nonlooped/roblox-suite/roblox-networking)<a href="https://agentmods.dev/skills/nonlooped/roblox-suite/roblox-networking"><img src="https://agentmods.dev/badge/skills/nonlooped/roblox-suite/roblox-networking/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/skills/nonlooped/roblox-suite/roblox-networking"><img src="https://agentmods.dev/badge/skills/nonlooped/roblox-suite/roblox-networking.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.00036 | $0.01395 |
| Opus 5.5 | $0.00014 | $0.00558 |
| Sonnet 5.5 | $0.00007 | $0.00279 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
roblox-networking 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
roblox-networking
Core sources: https://create.roblox.com/docs/projects/client-server , https://create.roblox.com/docs/scripting/security/security-tactics (server-authority techniques), the entire scripting/security/ section (security-tactics, defensive-design, client-server-boundary, network-ownership, access-control, etc.), events/remote and bindable, plus the relevant Engine classes (RemoteEvent, RemoteFunction, Bindable*, RunService, etc.).
Authority boundary
The server is authoritative for game state and simulation. The client simulates for responsiveness and renders what the server tells it. Anything that can be abused (economy, progression, combat outcomes, movement in competitive play) must be validated or simulated on the server.
Communication tools
RemoteEvent. Fire-and-forget across the boundary.
- Client → Server:
RemoteEvent:FireServer(...)→ server handler receives(player, ...) - Server → Client:
FireClient(player, ...)orFireAllClients(...)
RemoteFunction. Request/response (yields).
- Client:
InvokeServer(...)→ serverOnServerInvoke(player, ...) - Server can InvokeClient (less common, has caveats).
Critical warning:
RemoteFunction:InvokeClientyields the server until the targeted client returns a value. A hostile or lagging client can leave the invocation pending and hang the server indefinitely. Avoid server→client invocation; if you must use it, enforce a timeout and treat the client as untrusted.
BindableEvent / BindableFunction. Same-side only (server modules talking to each other, or client modules). They stay on one side of the network boundary.
General rule: Client sends intent. Server decides outcome and replicates the result (or lets normal Instance replication handle it).
Server authority techniques
- Validate every client action (distance, rate, prerequisites, stamina, line-of-sight, etc.).
- Simulate critical systems on the server (or at least re-execute the important parts).
- Use server tables or Attributes as source of truth, not leaderstats or client-visible values.
- For movement/physics in competitive games: rely on Roblox physics + network ownership + server validation/correction.
- Replicate only what each client needs (don't broadcast entire inventories every frame).
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -2 lines · -45 tokens per session a97588b16fd1
- 1mo ago First seen · 95 lines · 81 tokens per session scan A 015cb6942847
roblox-networking is a skill published in the GitHub repository nonlooped/roblox-suite (23 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 1,395 once invoked, about $0.0001 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-30.
Other skills, from other repositories
roblox-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/game-test-protocol.md 2>/dev/null || true !cat skills/shared/protocols/quality-gate.md 2>/dev/null || true !cat…
roblox-dev-skill
Verified, current Roblox and Luau knowledge for writing, reviewing and debugging Roblox game code. Use it for ANY task that involves Roblox, Luau or Roblox Studio, even a quick question or a one-line snippet: scripts and modules, RemoteEvents, DataStores and ProfileStore, ProcessReceipt and monetization, UI, the Input…
roblox-best-practices
Roblox and Luau game code standards. Writes, reviews, and fixes Script, LocalScript, and ModuleScript code and game systems such as shops, DataStore saves, RemoteEvents, combat, NPCs, and UI. Use when a request involves Luau code or a Roblox Studio project, even when Roblox is never named, when a game bug is reported…
rbx-dev
Meta-skill for complete Roblox game development with Rojo — the entry point that knows and unifies the three specialist skills /rojo (filesystem→Studio sync, project setup), /rbx-studio (editor, MCP, assets, malware scan) and /game-design (roles, workflows, GDD). Use this skill for ANY Roblox game-dev undertaking…
rojo
Operating Rojo — the filesystem-to-Roblox-Studio sync tool for professional Roblox development in VS Code / Claude Code instead of the Studio editor. Use this skill whenever Rojo is involved: rojo serve/rojo build, writing or debugging default.project.json, rokit/rokit.toml and tool versions (Rojo, Lune, Wally)…
roblox-studio
Build, inspect, repair, validate, and playtest Roblox Studio maps and Luau through the local bridge. Use for SceneSpecs, terrain, Studio edits, gameplay objects, visual checks, and Rojo output.