- Home
- Skills
- Game Development
- Redeem-Code Shop for Web Games
More screenshots
Works with the AI Agents you already use
Redeem-Code Shop for Web Games
Sell extras in a free web game with no backend: signed redeem codes sold as files, verified in-game, entitlements kept safe from save resets.
$5
Redeem-Code Shop for Web Games
Example session with this skill installed
I have a free browser game with an Android WebView wrapper. No backend, no accounts. I want to sell a $1 coin pack, a $4 bigger pack, and a $6 supporter tier with a cosmetic skin. Design the shop with this skill: catalog, storage, redeem behavior, and how you would prove it works before launch.
- Read your context and instructions
- Compiled the redeem-code shop
Catalog first, using the template. Currency: "coins," earned never, bought only. SKUs: PACK100 at $1.00 (the marketplace file-price floor — a $0.99 label will not save) granting 100 coins; PACK550 at $4.00 granting 550; SUPPORTER at $6.00 granting a supporter flag, the cosmetic skin, and 250 coins. Premium items priced in coins and flagged premium so earned currency can never buy them: the skin at 300 (also granted directly by the supporter code), a hint bundle at 80, a theme at 150.
Storage: one shop state object { balance, supporter, redeemed: { nonce: timestamp } } under its own localStorage key, game_shop_v1, kept out of the game save so a new game or save reset cannot delete purchases. Every field loads defensively and falls back to its default if malformed.
Redeem: input is trimmed and uppercased before a strict format check (pasted codes arrive with stray spaces and newlines — that is a support ticket, not a security event). Then decode, verify the Ed25519 signature with the pure-JS verifier against the embedded public key, look up the SKU grant, reject a nonce already in redeemed with reason used, otherwise apply the grant and record the nonce. Every outcome returns { ok, reason } so the UI says exactly what happened.
Proof before launch, per the smoke contract: starting balance exactly 0; smoke code redeems to exactly 100; the same code again fails as used; a code with one payload character flipped fails signature verification; buying the 80-coin hint bundle with 100 leaves exactly 20; PACK550 brings the balance to 570; the supporter code sets the flag, grants the skin with no purchase, and raises the balance to 820; reload and every value persists; zero console errors for the whole run. Minting happened offline, the private key sits outside the game tree at mode 0600, and the shipped build greps clean for private key material.
Connects securely to your tools. The creator never sees your data.
About this skill
Your game is free, offline, and has no server, no accounts, and no payment SDK — but you still want to sell a currency pack, a cosmetic, or a supporter tier. This skill gives you the zero-backend route: Ed25519-signed redeem codes, one per product, sold as small text files on a marketplace page you already have. The buyer pastes the code into the game, a pure-JavaScript verifier checks the signature locally, and the entitlement lands in a localStorage store that is deliberately separate from the game save, so starting a new game never wipes a purchase.
Inside: the signed-payload code format and why verification needs no database; an offline minting setup that keeps the private key out of the game tree, the APK, and version control; the shop module design with premium routing so earned currency can never buy paid items; a decision table for when this design fits and when you need an issuer service or store billing instead; a fill-in catalog template and pre-launch checklist; and a smoke-test contract that asserts exact credit balances at every step — redeem, re-redeem rejection, tampered-code rejection, insufficient-funds purchase, reload persistence — with zero console errors allowed. A complete worked example carries a fictional puzzle game from catalog to a passing smoke run.
The limits are stated plainly: one code per product means codes can be shared, and the skill helps you price and design for that instead of pretending it is DRM. If you need per-buyer codes or in-game refunds, it tells you what to build instead.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.
One code per product means every buyer of a pack gets the same code, and shared codes will work on any device — this is a courtesy-grade paywall, priced and designed for honestly. Codes cannot be revoked, attributed to a buyer, or counted per buyer; sales numbers come from the marketplace, not the game. There are no in-game refunds or chargebacks; the marketplace is the merchant of record. Entitlements live per device store, so a code can be redeemed again on a fresh device or after site data is cleared. Per-buyer codes require an issuer service, which the skill scopes but does not build.
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 buying a skill.
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 24 days ago