More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    timebomb

    1

    Find and reproduce temporal failures caused by time passage, expired state, and calendar boundaries.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    timebomb

    timebomb

    Example session with this skill installed

    Audit the subscription renewal logic in this repo. Check what happens if a user's payment fails at the end of the month and they try to renew two days later.

    • Read your context and instructions
    • Compiled the timebomb

    I have audited the subscription renewal logic located in src/services/billing.ts and src/models/Subscription.ts. I established a test boundary using the existing Jest suite and an injected clock seam.

    Temporal Audit Report: Subscription Renewal

    Execution Summary

    • Scenarios selected: 5
    • Scenarios executed: 5
    • Confirmed failures: 1
    • Supported concerns: 1
    • Passing scenarios: 3

    Findings

    ID-01: Grace Period Access Leak (CONFIRMED)

    • Severity: Medium
    • Source: src/services/billing.ts:88

    Observation: When a payment fails on Jan 31, the system correctly marks the status as past_due. However, the middleware check isSubscriptionActive() returns true for 48 hours regardless of the actual plan expiry date, because it uses a hardcoded 2-day offset from Date.now() instead of the expiresAt field.

    • Reproduction: npm test tests/temporal/billing-leak.spec.ts
    • Result: Access allowed at T+49h when T was Jan 31.

    Scenario Ledger

    IDFeatureBoundary or SequenceClock ControlsResultEvidence
    TS-01Month-end RenewalJan 31 to Feb 28Injected DatePASSRuntime match
    TS-02Payment FailureExpiry + 48hFake TimersFAILCONFIRMED
    TS-03Manual RetryPost-failureStored FixturePASSRuntime match

    Next steps

    1. Review the proposed fix in src/services/billing.ts to replace Date.now() with the storedExpiry reference.
    2. Run the new regression test tests/temporal/billing-leak.spec.ts to verify the fix.
    3. Define the policy for leap year renewals (Feb 29) which currently defaults to March 1.

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

    About this skill

    Time-based bugs often stay hidden until a demo ends, a trial expires, or a new year begins. This skill audits how your application handles the passage of time, stale state, and event ordering. It moves beyond simple date formatting checks to investigate complex temporal logic like subscription renewals, cache expirations, and race conditions in delayed webhooks.

    What it does

    • Temporal Inventorying maps every feature to its clock source, stored state, and boundary conditions.
    • Failure Reproduction builds deterministic test cases for scenarios like February 29th transitions or month-end billing cycles.
    • Clock Modeling identifies and isolates browser, server, database, and provider clocks to test multi-tier synchronization.
    • Evidence-Backed Auditing classifies findings as confirmed failures, supported concerns, or policy gaps based on runtime behavior.
    • Automated Regression Testing generates local integration or browser tests to prevent temporal regressions.

    How it works

    1. Execution Boundary Setup identifies your test framework, runtimes, and local mocks to ensure safe, isolated testing.
    2. Scenario Selection chooses high-impact paths like session expiry or scheduled job catch-up based on your repository source.
    3. Contract Definition establishes the expected behavior and clock controls before running any code.
    4. Audit Delivery generates a mandatory report detailing confirmed bugs, evidence levels, and remaining exposure.

    Frameworks & tools

    Primary support for JavaScript and TypeScript environments. Works with Playwright, Node.js, and standard testing libraries to implement clock seams and dependency injection.

    Why this beats prompting it yourself

    Generic prompts often miss subtle edge cases like IANA timezone transitions or the difference between elapsed duration and calendar rules. This skill enforces a rigorous evidence classification system, ensuring you never mistake a static code guess for a verified runtime bug.

    Use cases

    • Subscription Audits to verify users lose access exactly when their trial ends.
    • Dashboard Refresh Testing to see how UI components handle stale data or midnight rollovers.
    • Webhook Sequencing to ensure late-arriving events don't overwrite newer authoritative state.
    • Background Job Verification to check if missed cron tasks catch up correctly.

    Known limitations

    Does not change the OS clock or modify production records. External provider simulation is limited to available test-clock APIs or local mocks. Code inspection is prioritized for JS/TS repos.

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

    Focuses on JS/TS. Cannot modify OS clock or live production data. Execution depends on local test framework availability. Only tests temporal logic, not general business logic.

    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 27 days ago

    Permissions

    Browser
    Read Files
    Network Access
    Terminal / Shell
    Write Files

    File Scopes

    Add
    **/*
    relative
    to
    the
    buyer’s
    selected
    project
    directory.
    TIMEBOMB
    may
    inspect
    source
    tests
    configuration
    and
    schemas
    across
    different
    folder
    layouts.

    Reads the selected project's source, tests, and configuration. Uses the terminal to run local tests and writes audit reports or regression tests. Changes application code when fixes are requested. Browser and network access are only needed for scenarios involving a running app or service sandbox. No connected accounts or production credentials are required for the basic local workflow.

    Listed27 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the detection of bugs related to time passage, such as trial expirations, leap year transitions, and race conditions in delayed webhooks, which are often missed by standard unit tests.

    Timebomb is designed for AI agents operating in JavaScript and TypeScript environments and integrates seamlessly with common testing frameworks like Playwright and Node.js.

    No, the skill operates by creating clock seams and using dependency injection within your test framework, ensuring it never modifies your OS clock or production data.

    The skill includes the core temporal inventorying logic, failure reproduction templates, and a reporting module that classifies findings into confirmed failures or policy gaps.

    While optimized for JS/TS repositories, the skill can audit multi-tier architectures by identifying and isolating clock sources across browsers, servers, and databases.

    New in Testing & Debugging