- Home
- Skills
- Game Development
- Roblox Luau Safety Check
More screenshots
Works with the AI Agents you already use
Roblox Luau Safety Check
This skill finds those and the other Roblox mistakes below before you publish, and tells you how to fix each one.
$5
Roblox Luau Safety Check
Example session with this skill installed
Check this project with roblox-luau-safety-check.
- Read your context and instructions
- Compiled the roblox luau safety
$ python3 scripts/check_roblox.py examples/risky
BLOCK default.project.json:12 R02 LOADSTRING_USED
"LoadStringEnabled": true
Why: loadstring runs a string as Luau code, and ServerScriptService.LoadStringEnabled turns it on (it is off by default and Roblox recommends keeping it off). Any path from a remote, an HTTP response or a DataStore value into that string lets someone else run code on your server; backdoors in free models use it the same way.
Safer: Remove loadstring and keep LoadStringEnabled false. Put the logic in ModuleScripts in your project and choose behaviour from data (a table of allowed actions).
BLOCK src/server/Admin.server.luau:6 R03 REQUIRE_BY_ASSET_ID
BLOCK src/server/Admin.server.luau:14 R02 LOADSTRING_USED
BLOCK src/server/Combat.server.luau:9 R01 CLIENT_VALUE_WRITTEN_TO_STATS
BLOCK src/server/Logging.server.luau:5 R05 ACCOUNT_COOKIE_IN_CODE
BLOCK src/server/Shop.server.luau:14 R01 CLIENT_VALUE_WRITTEN_TO_STATS
BLOCK src/server/Shop.server.luau:24 R01 CLIENT_VALUE_WRITTEN_TO_STATS
BLOCK src/shared/Config.luau:4 R04 SECRET_IN_CLIENT_CODE
BLOCK src/shared/Config.luau:5 R04 SECRET_IN_CLIENT_CODE
REVIEW src/server/Admin.server.luau:9 R14 GETFENV_SETFENV
REVIEW src/server/Admin.server.luau:10 R16 OBFUSCATED_OR_HIDDEN_CODE
REVIEW src/server/Combat.server.luau:6 R11 REMOTE_ARGS_NOT_VALIDATED
REVIEW src/server/Combat.server.luau:18 R18 CLIENT_INSTANCE_CHANGED
REVIEW src/server/Combat.server.luau:23 R13 INVOKE_CLIENT
REVIEW src/server/Logging.server.luau:4 R17 POSSIBLE_SECRET_IN_CODE
REVIEW src/server/Purchases.server.luau:7 R20 PURCHASE_GRANTED_OUTSIDE_PROCESSRECEIPT
REVIEW src/server/Shop.server.luau:11 R11 REMOTE_ARGS_NOT_VALIDATED
REVIEW src/server/Shop.server.luau:11 R12 REMOTE_WITHOUT_RATE_LIMIT
REVIEW src/server/Shop.server.luau:23 R12 REMOTE_WITHOUT_RATE_LIMIT
REVIEW src/server/Shop.server.luau:24 R15 DATASTORE_CALL_WITHOUT_PCALL
REVIEW src/server/Shop.server.luau:32 R15 DATASTORE_CALL_WITHOUT_PCALL
REVIEW src/server/Signs.server.luau:9 R19 UNFILTERED_TEXT_SHOWN
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 9 files, 9 with Roblox Luau content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A shop remote that runs coins.Value -= price with the price the client sent lets any exploiter buy a sword for -1000 coins and walk away richer, and a Discord webhook in a ModuleScript under ReplicatedStorage can be read by every player who decompiles it. This skill finds those and the other Roblox mistakes below before you publish, and tells you how to fix each one.
Your agent runs a scanner on your .luau and .lua files and your Rojo project files (default.project.json and other *.project.json / .jsonc files). It reads the project file to learn where each folder lands in the game, so it knows which LocalScripts and ModuleScripts players receive and which code stays on the server; without a project file it uses Rojo's usual src/server, src/client and src/shared folders and the .server.luau / .client.luau names. It understands Luau strings, interpolated strings, if-then-else expressions and type annotations, follows client arguments through local variables in OnServerEvent, OnServerInvoke, Knit client methods and Comm handlers, treats a price the server looks up (ShopItems[itemName].Price) as the server's value, and skips installed packages. It never runs your code or contacts Roblox. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach, and the rules guide links the official Roblox page behind each rule. Secrets are never printed.
What it checks
It has 5 BLOCK and 10 REVIEW rules.
BLOCK
- R01: a remote handler writes a value the client sent into leaderstats, a currency or stat field, health (TakeDamage), saved data (profile.Data, including Data[key] = value with a client key), a stat attribute, a stat helper such as AddCoins or coinStore:Increment, or a DataStore write (UpdateAsync judged inside its transform), without a fixed limit, a clamp, a server lookup or a validator
- R02: loadstring, or LoadStringEnabled turned on in a script or in the Rojo project file
- R03: require() of an asset ID (a number, hex, tonumber(...), or a name set to a number), the classic free-model backdoor
- R04: webhook URLs, keys or tokens in URL queries, Authorization headers, and key-shaped values under key, token, secret or password names, in a LocalScript or a ModuleScript that replicates to players (game words such as TokenShop_v2 are left alone)
- R05: a .ROBLOSECURITY account cookie anywhere in the code
REVIEW
- R11: remote arguments used with no run-time check (type annotations are not checks), and numbers that reach stats after range checks but with no NaN check
- R12: remote handlers that do costly work (Async calls, Instance.new, Clone) in a file with no cooldown or rate limit
- R13: RemoteFunction:InvokeClient
- R14: getfenv or setfenv
- R15: DataStore calls outside pcall, a Promise or a retry helper
- R16: obfuscated or hidden code: long escaped byte strings, long string.char lists, long encoded strings, code pushed off-screen with spaces
- R17: the same secrets as R04 in server code or in scripts whose place in the game cannot be told, and values under secret names that may be secrets but do not look like generated keys
- R18: a remote handler destroys, moves or re-parents an Instance the client passed, or changes the health or stats of an Instance the client picked, without checking that it belongs to the player or is in range
- R19: player text from a remote put on a TextLabel or sent to all clients in a file that never filters text
- R20: developer product rewards given in PromptProductPurchaseFinished instead of ProcessReceipt, or a LocalScript that asks the server for them from that event
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official Roblox documentation link for each rule
- A risky and a safe example Rojo project, and the real report the scanner produces on the risky one
Limits It reads each file as written and follows client values through local variables inside one handler, not into other modules, so checks done in a shared validation module, middleware or remote libraries such as BridgeNet, ByteNet, Red, Zap or Blink are not seen, and handlers registered through those libraries are not analysed. Stats are recognised by whole words in their names (Coins, Cash, Gems, XP, Level, Wins and similar), so a currency with an unusual name can be missed, and secrets under unusual names are not reported. A rate limit or text filter anywhere in a file counts for every handler in it. Place files (.rbxl, .rbxm) and Studio settings outside the project file are not read. Roblox's own remote example (a part made from the client's colour and position) gets R11 and R12 on purpose. NOT FLAGGED is not a guarantee.
Static check of file text. Values passed between modules, remote wrapper libraries, place files and Studio settings outside the Rojo project file are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert values (NOT-A-REAL-..., EXAMPLE) for the scanner to find, including a fake webhook, a fake key, a fake cookie value and a made-up asset ID. Nothing in it is run.