agentleFS
Sign inStart free
AshExplainedAshExplained/roblox-skills/roblox-security-economy/SKILL.md

roblox-security-economy

Skill5 starsChanged 5 months agoMITView on GitHub

Build and review Roblox security-sensitive economy systems. Use for currency, inventory, DataStores, trading, purchases, rewards, anti-dupe logic, RemoteEvent validation, server authority, receipt handling, and exploit-resistant progression.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat client UI as display and intent only.

    line 26
  2. Distinctive:

    Use idempotency for purchases and valuable grants.

    line 27
  3. Distinctive:

    Use versioned data schemas and migration guards.

    line 33
  4. Distinctive:

    Use server-owned trade sessions.

    line 40
  5. Distinctive:

    Commit atomically from server state where possible.

    line 44
  6. Very specific:

    Use script_grep for remotes, currency names, DataStore usage, receipt handlers, and grant functions.

    line 49
  7. Very specific:

    Read every script that touches value with script_read.

    line 50
  8. Very specific:

    Verify the protected flows in a playtest with roblox-playtest-qa, and confirm the save path is safe with roblox-datastore-persistence.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Roblox Security Economy

Goal

Protect valuable game state while keeping the player loop fair. Anything that grants, spends, trades, saves, or purchases value must be server-authoritative.

High-Risk Surfaces

  • Currency and premium currency.
  • Inventory, pets, skins, tools, boosts, and quest rewards.
  • Trading, gifting, crafting, upgrades, prestige, and loot rolls.
  • Developer product receipts and game pass checks.
  • Daily rewards, streaks, event rewards, and group rewards.
  • Client remotes that request grants, damage, teleport, placement, or progression.

Server Authority Rules

  • Calculate rewards on the server.
  • Validate player eligibility on the server.
  • Store canonical balances and inventory on the server.
  • Treat client UI as display and intent only.
  • Use idempotency for purchases and valuable grants.
  • Reject malformed, replayed, impossible, or too-frequent remote requests.

DataStore And Receipt Patterns

  • Save compact canonical state, not UI state.
  • Use versioned data schemas and migration guards.
  • Queue or debounce saves during active sessions.
  • Bind saves to player leaving and server shutdown paths.
  • For developer products, grant through receipt processing and record processed purchase IDs before considering the transaction complete.

Trading And Gifting

  • Use server-owned trade sessions.
  • Lock offered items while a trade is pending.
  • Require both parties to confirm the exact final offer.
  • Revalidate ownership immediately before commit.
  • Commit atomically from server state where possible.
  • Log valuable trades and grant paths for later investigation.

MCP Review Workflow

  1. Use script_grep for remotes, currency names, DataStore usage, receipt handlers, and grant functions.
  2. Read every script that touches value with script_read.
  3. Inspect relevant instances with search_game_tree and inspect_instance.
  4. Patch with multi_edit only after mapping source-to-sink flow.
  5. Playtest purchase-free paths and console errors with start_stop_play and get_console_output.

Output

Report:

  • Assets or values protected.
  • Trust boundary.
  • Server validation rules.
  • Abuse cases prevented.
  • Remaining risks or manual Roblox purchase tests.

Next

Verify the protected flows in a playtest with roblox-playtest-qa, and confirm the save path is safe with roblox-datastore-persistence.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free