AgentStack
SKILL verified MIT Self-run

Remotes Audit

skill-codephobiia-claude-roblox-game-studio-remotes-audit · by CodePhobiia

Audit all RemoteEvent and RemoteFunction usage for security, correctness, and bandwidth efficiency. Checks for server-side validation, rate limiting, type checking, and anti-exploit patterns.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-codephobiia-claude-roblox-game-studio-remotes-audit

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Remotes Audit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

/remotes-audit — Remotes Security Audit

Delegate to: remotes-networking-specialist (with exploit-security-specialist for security review)

Steps:

  1. Find all RemoteEvent/RemoteFunction creation: grep -rn "RemoteEvent\|RemoteFunction\|UnreliableRemoteEvent" src/
  2. Find all OnServerEvent handlers: grep -rn "OnServerEvent\|OnServerInvoke" src/
  3. Find all FireServer calls: grep -rn "FireServer\|InvokeServer" src/

For each server-side handler, verify:

Critical (must fix):

  • [ ] Type checking on EVERY argument (typeof(arg) == expected)
  • [ ] Range/sanity checks on numeric values
  • [ ] Player reference validation (is this player allowed to do this?)
  • [ ] No RemoteFunction with OnServerInvoke from client (server hang risk)

Important (should fix):

  • [ ] Rate limiting per player (configurable, recommended 10-30 calls/sec depending on remote)
  • [ ] Cooldown enforcement server-side (not relying on client cooldown)
  • [ ] No Instance references passed through remotes (use string keys/IDs)
  • [ ] Bandwidth estimation for high-frequency remotes

Architecture:

  • [ ] Remotes manifest exists and is up to date (design/remotes-manifest.md)
  • [ ] Remotes centrally managed (not scattered Instance.new calls)
  • [ ] Clear naming convention for remotes

Output:

Generate a security report with findings organized by severity:

# Remotes Audit

## Summary
- Total remotes found: X
- Client → Server: X
- Server → Client: X
- Unreliable: X

## Remotes Inventory
| Name | Type | Direction | Validation | Rate Limit | Status |
|------|------|-----------|------------|------------|--------|
| PurchaseItem | RemoteEvent | C→S | ✅ | ✅ 5/sec | OK |
| ShowMessage | RemoteEvent | S→C | N/A | N/A | OK |
| RequestData | RemoteFunction | S→C | N/A | N/A | OK |
| DangerousRemote | RemoteFunction | C→S | ❌ | ❌ | ⚠️ CRITICAL |

## Critical Findings
1. **DangerousRemote** (`src/ServerScriptService/X.lua:42`)
   - Client → Server RemoteFunction — server hang risk
   - Fix: Convert to RemoteEvent with optional response via separate remote

## Important Findings
...

## Recommendations
- Create `design/remotes-manifest.md` if missing
- Consolidate remote creation into `ReplicatedStorage/Shared/Remotes.lua`

Offer to delegate fixes to the appropriate specialist.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.