agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/exploit-check/SKILL.md

exploit-check

Skill9 starsChanged 7 months agoMITView on GitHub

Run a comprehensive security audit checking for common Roblox exploit vectors including movement hacks, remote exploitation, economy exploits, and data manipulation.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search for any client-side game state that the server doesn't validate

    line 13
  2. Distinctive:

    Check: currency changes, inventory modifications, health/damage

    line 14
  3. Very specific:

    Run /remotes-audit as a sub-step

    line 23
  4. Distinctive:

    Check if player position is server-validated

    line 27
  5. Distinctive:

    Check for speed limits, teleport distance limits

    line 28
  6. Distinctive:

    Check for item duplication vectors (race conditions in trades)

    line 37
  7. Distinctive:

    Check for negative quantity exploits

    line 38
  8. Distinctive:

    Verify MarketplaceService ProcessReceipt is server-authoritative

    line 39
  9. Distinctive:

    Check for currency overflow (number limits in Luau: 2^53)

    line 40
  10. Distinctive:

    Check for data loss vectors

    line 49
  11. Distinctive:

    Verify no sensitive data in client-accessible locations (ReplicatedStorage, StarterGui, etc.)

    line 50

≈ “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

/exploit-check — Security Vulnerability Scan

Delegate to exploit-security-specialist agent to run a full audit.

Scan Areas:

1. Client Trust Analysis

  • Search for any client-side game state that the server doesn't validate
  • Check: currency changes, inventory modifications, health/damage
  • Flag any game.Players.LocalPlayer mutations that affect game state
grep -rn "LocalPlayer" src/StarterPlayer/ --include="*.lua" --include="*.luau"
grep -rn "Humanoid.Health\s*=" src/ --include="*.lua" --include="*.luau"

2. Remote Security

  • Run /remotes-audit as a sub-step
  • Additionally check for remotes that could be replayed or spoofed

3. Movement Security

  • Check if player position is server-validated
  • Check for speed limits, teleport distance limits
  • Identify if fly/noclip is preventable with current architecture
grep -rn "HumanoidRootPart.CFrame\s*=" src/
grep -rn "WalkSpeed\s*=\|JumpPower\s*=\|JumpHeight\s*=" src/

4. Economy Security

  • Check for item duplication vectors (race conditions in trades)
  • Check for negative quantity exploits
  • Verify MarketplaceService ProcessReceipt is server-authoritative
  • Check for currency overflow (number limits in Luau: 2^53)
grep -rn "ProcessReceipt" src/
grep -rn "UserOwnsGamePassAsync" src/

5. Data Security

  • Run /datastore-review as a sub-step
  • Check for data loss vectors
  • Verify no sensitive data in client-accessible locations (ReplicatedStorage, StarterGui, etc.)
grep -rn "ADMIN_LIST\|admin_list\|adminList" src/ReplicatedStorage/
grep -rn "API_KEY\|apikey\|api_key" src/

Output:

Generate an exploit report using .claude/docs/templates/exploit-report-template.md. Classify findings as Critical / High / Medium / Low.

Severity Classification

  • Critical: Data loss, account takeover, financial exploit, full admin escalation
  • High: Significant gameplay impact (god mode, unlimited currency, item dup)
  • Medium: Noticeable but limited (visual hacks that affect gameplay, rate limit bypass)
  • Low: Minor (UI manipulation that doesn't affect other players)

For each finding, report:

  • Severity
  • Attack vector (how is this exploited?)
  • Affected files
  • Mitigation (specific code change)
  • Verification steps (how to confirm the fix works)

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.