More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Stop Crosstenant Cache Leaks

    1

    Repair cache bugs that expose one customer’s data to another tenant or return stale results after writes.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Stop Crosstenant Cache Leaks

    Stop Crosstenant Cache Leaks

    Example session with this skill installed

    Our Redis cache is leaking data between organizations. When Org A updates their project list, Org B sometimes sees Org A's stale projects. Fix the key scoping and invalidation.

    • Read your context and instructions
    • Compiled the stop crosstenant cache

    I identified that the 'project_list' key was missing a tenant identifier. I modified ProjectRepository.js to use a scoped key: 'env:tenant_id:projects:v1'. I also added a precise invalidation call in the UpdateProject service and verified that Org B no longer sees Org A's data.

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

    About this skill

    The problem

    Multi-tenant applications often leak sensitive data when cache keys lack proper scoping or invalidation logic. Developers face cross-tenant data collisions, stale reads after updates, and authorization bypasses during cache hits.

    What it does

    • Audits Redis, Memcached, and in-memory caches for unsafe key construction.
    • Traces cached values from storage to retrieval to ensure authorization boundaries are respected.
    • Applies tenant-scoped cache key contracts and precise invalidation triggers.
    • Implements stampede protection and namespace versioning to prevent performance degradation.
    • Validates repairs using concurrent request simulations and cross-tenant leakage tests.

    Frameworks & tools

    Supports Redis, Memcached, CDN layers, and framework-specific query or response caches. Works with any standard tenant model involving organization, workspace, or user identifiers.

    Why this beats prompting it yourself

    Generic prompts often miss subtle race conditions or fail to verify if a cache hit bypasses server-side authorization. This skill follows a strict execution process that mandates cross-tenant testing and precise invalidation over simple TTL-based fixes.

    Use cases

    • Preventing User A from seeing User B's cached dashboard data.
    • Fixing stale permission caches after a user's role has been revoked.
    • Ensuring search results remain isolated within a specific organization's namespace.
    • Protecting authoritative databases from stampedes during high-concurrency cache misses.

    Known limitations

    Requires server-side validation of tenant identifiers. Cannot verify distributed behavior if only local mocks are available without access to the actual cache provider.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires server-side tenant validation. Cannot verify distributed behavior if only local mocks are available. Claims of isolation require cross-tenant test execution.

    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 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 3 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Permissions are limited to the active local workspace and are used to inspect user-supplied or local workspace files; create or modify bounded local fixes, tests, documentation, or review artifacts; run repository-supported local tests, checks, builds, or parsing commands. The skill package does not require bundled credentials, unrestricted external network access, or automatic production changes.

    Listed3 months ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill audits your caching architecture (Redis, Memcached, etc.) to identify where keys lack proper tenant scoping, preventing sensitive data from User A being served to User B. It then implements robust key contracts and invalidation triggers to ensure data isolation and freshness.

    Yes, the skill is designed to work with any standard tenant model, whether you isolate data by Organization ID, Workspace ID, or individual User ID, and can apply these scopes across various caching layers.

    You will receive the AI agent skill configuration, a suite of automated audit procedures, and a validation framework that uses concurrent request simulations to verify the repairs. It includes pre-defined patterns for Redis, Memcached, and CDN-level caching.

    The skill requires access to your application's cache configuration and server-side tenant identifiers; however, it cannot verify distributed behavior if it is restricted to local mocks without access to the actual cache provider.

    Unlike generic prompts, this skill follows a strict security protocol that mandates cross-tenant leakage testing and addresses complex issues like race conditions and cache stampedes that simple TTL fixes miss.

    New in Agents & Orchestration