More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    RBsmithy pro

    2

    Production engineering and security auditor for Roblox and Rojo Luau projects.

    $19.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    1 useSecurity scanned
    RBsmithy pro

    RBsmithy pro

    Example session with this skill installed

    Review my RemoteEvent handling in the 'Combat' folder for potential exploit risks and suggest a secure validation pattern.

    • Read your context and instructions
    • Compiled the rbsmithy pro

    I have completed a boundary audit of the RemoteEvent logic in src/server/Combat/ and src/client/Combat/. The review focused on ownership validation and rate limiting.

    Remote Security Audit

    RemoteClient ClaimServer TruthValidationRate Limit
    DealDamageTarget, DamageWeapon StatsRaycast/Magnitude5/sec
    UseAbilityAbilityIDCooldown Stateos.clock() check1/sec

    Secure Validation Implementation

    -- src/server/Combat/DamageHandler.lua
    local RE_DEAL_DAMAGE = ReplicatedStorage.Remotes.DealDamage
    
    RE_DEAL_DAMAGE.OnServerEvent:Connect(function(player, target, claimedDamage)
        -- VULNERABILITY FOUND: server was trusting 'claimedDamage' from client
        local character = player.Character
        if not (character and target and target:IsDescendantOf(workspace)) then return end
    
        -- Validation: Magnitude check
        local dist = (character.PrimaryPart.Position - target.Position).Magnitude
        if dist > 20 then return end 
    
        -- Validation: Server-owned truth for damage
        local weapon = player.EquippedWeapon.Value
        local actualDamage = WeaponConfig[weapon].BaseDamage
        
        target.Humanoid:TakeDamage(actualDamage)
    end)
    

    Next steps

    1. Replace claimedDamage parameters with server-side lookups in all Combat remotes.
    2. Implement a basic magnitude check to prevent "kill-all" exploits.
    3. Verify the fix in Studio using a local server with two clients to test reachability.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Roblox games often suffer from exploitable RemoteEvents, data loss in DataStore, and botched releases. This skill provides a specialized production engineering auditor and release playbook for developers working in Luau and Rojo.

    What it does

    • Exploit auditing identifies unsafe client-to-server boundaries and validates RemoteEvent security.
    • Data integrity review analyzes DataStore patterns to prevent session contention and player data loss.
    • Release gating generates Go/No-Go checklists based on multiplayer regression and performance budgets.
    • Incident response provides structured triage workflows for live crashes and production regressions.
    • Automated scanning utilizes a read-only Luau auditor to surface high-priority risks in local repositories.

    How it works

    1. Inspection scans default.project.json and Rojo mappings to establish the server-client boundary.
    2. Audit runs a Python-based static analysis or manual file review to find vulnerabilities and persistence failures.
    3. Prioritization generates a triage table ranking findings by severity, player impact, and evidence.
    4. Remediation delivers reviewed Luau patches with explicit server/client ownership and rollback plans.

    Frameworks & tools

    Built for Roblox Studio and Rojo workflows. Requires Python 3.11 for the automated auditor script. Works with Luau, DataStoreService, and MarketplaceService.

    Why this beats prompting it yourself

    Generic AI often suggests insecure patterns like client-side validation for currency or unsafe DataStore retries. This skill enforces strict server-owned truth and production-grade release gates derived from multiplayer engineering best practices.

    Use cases

    • Audit RemoteEvents before a major game update to prevent script injection.
    • Review purchase handling and receipt idempotency for developer products.
    • Create a multiplayer regression plan for new game features.
    • Diagnose and rollback live production incidents or performance spikes.

    Known limitations

    Does not execute Luau code or access the Studio DataModel directly. Static analysis cannot guarantee 100% exploit prevention or parse complex dynamic Luau semantics.

    Requires Python 3.11+ for the automated script. Does not provide automatic exploit prevention or direct Studio access. Limited to static analysis of Luau and Rojo files.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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

    1 use

    Times used to date

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Python

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    rbsmithy pro identifies critical vulnerabilities such as unsafe RemoteEvent boundaries, DataStore session contention, and purchase idempotency flaws that generic AI models often miss or incorrectly validate.

    The skill includes the specialized AI auditor persona, a Python-based static analysis script for local repository scanning, and a suite of production-grade release and incident response templates.

    Yes, it is specifically designed for Rojo-based workflows, scanning your `default.project.json` and file mappings to accurately differentiate between server and client logic.

    While the AI auditor performs deep static analysis, it operates in a read-only capacity and does not execute Luau code or access your live Studio DataModel, ensuring your source code remains secure.

    You will need a compatible AI agent host (like ChatGPT or Claude) to interact with the skill, plus Python 3.11 installed locally if you wish to run the automated repository scanning script.

    Purchasing rbsmithy pro grants you access to the current version of the auditor and playbooks, along with any maintenance updates or logic refinements released within the marketplace support window.

    New in Testing & Debugging