remotes-audit
Skill9 starsChanged 7 months agoMITView on GitHub
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.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
Files
/remotes-audit — Remotes Security Audit
Delegate to: remotes-networking-specialist (with exploit-security-specialist for security review)
Steps:
- Find all RemoteEvent/RemoteFunction creation:
grep -rn "RemoteEvent\|RemoteFunction\|UnreliableRemoteEvent" src/ - Find all OnServerEvent handlers:
grep -rn "OnServerEvent\|OnServerInvoke" src/ - 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

