testing-and-go-live

testing-and-go-live is a skill for Claude Code, Codex from dodopayments/dodo-agent-plugin. It costs 31 tokens per session (2,847 once invoked), scanned A, a copy of testing-and-go-live, MIT.

A guide for testing Dodo Payments integrations and preparing them for production. It covers separate test and live environments, payment and renewal simulations, local webhook tests, catalog migration, and launch checks.

In plain words
What is it for?
Use it to test successful and failed payments, subscription renewals, regional payment methods, local webhooks, test-to-live product copying, and production readiness.
Why use it?
It helps find payment-flow problems before real customers and prevents test data, keys, and webhooks from being confused with live ones.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Part of the dodopayments plugin — 17 skills, 2 MCP servers shipped together

Good fit Use it to test successful and failed payments, subscription renewals, regional payment methods, local webhooks, test-to-live product copying, and production readiness.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dodopayments/dodo-agent-plugin/testing-and-go-live
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add dodopayments/dodo-agent-plugin --skill testing-and-go-live
Clone the repo
git clone --depth 1 https://github.com/dodopayments/dodo-agent-plugin

Made for: Claude Code, Codex.

Or install dodopayments, the plugin that ships this one along with the rest of its 17 skills, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for testing-and-go-live

README.md
[![agentmods](https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/testing-and-go-live.svg)](https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/testing-and-go-live)
Your own site
<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/testing-and-go-live"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/testing-and-go-live.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,847 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.02847
Opus 5 $0.00015 $0.01424
Sonnet 5 $0.00006 $0.00569
Haiku 4.5 $0.00003 $0.00285

Measured 7d ago against content hash 83ec85d34b5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

testing-and-go-live scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to testing-and-go-live — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/dodopayments/skills/testing-and-go-live/SKILL.md · 336 lines

How it starts

The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing and Go-Live

This skill covers test mode, test payment methods, webhook testing, and the production launch checklist. Use it when building payment flows that need verification before going live, or when preparing to switch from test to production.

When to use this skill

  • You need to test card success/decline scenarios, subscription renewals, or regional payment methods.
  • You're setting up webhook testing locally or in a staging environment.
  • You're preparing to launch to production and need a go-live checklist.
  • You want to verify that test and live environments are properly isolated.
  • You're copying products from test to production.

Core concepts

Test vs. live mode: Dodo Payments maintains two completely separate environments. Each has its own base URL, API keys, webhooks, products, customers, and transactions. Data does not carry over between them.

  • Test mode: https://test.dodopayments.com
  • Live mode: https://live.dodopayments.com

Each environment requires separate API keys issued from the dashboard. The SDK defaults to live_mode if you don't specify environment, which is a real footgun in development.

Test payment methods: Dodo documents specific card numbers, VPAs, and payment method scenarios for testing. These only work in test mode.

Webhook testing: The CLI provides commands to listen for webhooks locally and trigger test events without making real payments.


Setting up test mode

Always explicitly set environment: 'test_mode' during development. The default is live_mode.

import DodoPayments from 'dodopayments';

const client = new DodoPayments({
  bearerToken: process.env.DODO_PAYMENTS_API_KEY,
  environment: 'test_mode', // REQUIRED — defaults to 'live_mode'
});
from dodopayments import DodoPayments

client = DodoPayments(
    bearer_token=os.environ.get("DODO_PAYMENTS_API_KEY"),
    environment="test_mode",  # defaults to "live_mode"
)
client := dodopayments.NewClient(
    option.WithBearerToken("dodo_test_..."),
    option.WithEnvironmentTestMode(), // defaults to WithEnvironmentLiveMode()
)

Read the full file on GitHub · 336 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 336 lines · 31 tokens per session scan A 83ec85d34b5e

Subscribe to this mod's changes

testing-and-go-live is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 2,847 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to testing-and-go-live, differing in 0 lines, and is treated as a copy.