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.
npx skills add Venkateshwar-Reddy-Jambula/razorpay-integration-plugin --skill local-testinggit clone --depth 1 https://github.com/Venkateshwar-Reddy-Jambula/razorpay-integration-pluginWrote 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.
[](https://agentmods.dev/skills/venkateshwar-reddy-jambula/razorpay-integration-plugin/local-testing)<a href="https://agentmods.dev/skills/venkateshwar-reddy-jambula/razorpay-integration-plugin/local-testing"><img src="https://agentmods.dev/badge/skills/venkateshwar-reddy-jambula/razorpay-integration-plugin/local-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/venkateshwar-reddy-jambula/razorpay-integration-plugin/local-testing"><img src="https://agentmods.dev/badge/skills/venkateshwar-reddy-jambula/razorpay-integration-plugin/local-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00067 | $0.02053 |
| Opus 5 | $0.00034 | $0.01026 |
| Sonnet 5 | $0.00013 | $0.00411 |
| Haiku 4.5 | $0.00007 | $0.00205 |
Grade A, and why
local-testing scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -u rzp_test_xxxxx:your_test_secret \ How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Razorpay Testing Guide
Complete guide to testing your Razorpay integration locally before touching production.
Step 1: Get Test API Keys
- Go to Razorpay Dashboard
- Toggle to Test Mode (top-left switch)
- Go to Settings → API Keys → Generate Key
- You'll get:
rzp_test_xxxxx— Key ID- A secret — Key Secret (shown once, save it)
Update .env.local:
RAZORPAY_KEY_ID=rzp_test_xxxxx
RAZORPAY_KEY_SECRET=your_test_secret
NEXT_PUBLIC_RAZORPAY_KEY_ID=rzp_test_xxxxx
Test keys start with rzp_test_, live keys with rzp_live_. They access completely separate environments — test data is invisible in live mode and vice versa.
Step 2: Create Test Plans
Plans must exist before you can create subscriptions. Create them in test mode:
curl -u rzp_test_xxxxx:your_test_secret \
https://api.razorpay.com/v1/plans \
-H "Content-Type: application/json" \
-d '{
"period": "monthly",
"interval": 1,
"item": {
"name": "Pro Plan Monthly",
"amount": 99900,
"currency": "INR",
"description": "Pro plan billed monthly"
}
}'
Save the returned plan_id (e.g., plan_test_xxxxx) in your .env.local:
RAZORPAY_PLAN_MONTHLY=plan_test_xxxxx
Test and live plans have different IDs. You need separate plan IDs per environment.
Step 3: Set Up ngrok for Webhooks
Razorpay can't reach localhost. You need a public tunnel.
Install ngrok
# macOS
brew install ngrok
# or download from https://ngrok.com/download
# Sign up for free account and add authtoken
ngrok config add-authtoken your_token
Start the tunnel
# Start your app first
npm run dev # localhost:3000
# In another terminal, start ngrok
ngrok http 3000
ngrok gives you a URL like https://abc123.ngrok-free.app. This is your public URL.
Keep ngrok running throughout your testing session. If you restart ngrok, you get a new URL and must re-register the webhook.
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.
- 10d ago First seen · 223 lines · 67 tokens per session scan A 44f6db6f295c
local-testing is a skill published in the GitHub repository Venkateshwar-Reddy-Jambula/razorpay-integration-plugin (6 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 2,053 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
synthetic-monitoring
AI-powered synthetic monitoring skill for e-commerce websites. Designs automated user journey tests for add-to-cart, checkout, and payment flows with alerting rules and performance baselines.
visual-regression-testing
AI-powered visual regression testing skill for e-commerce websites. Designs screenshot comparison workflows, mobile/desktop visual checks, and change detection alerts to prevent conversion-killing UI bugs.
smoke-test-critical-paths
Quick Reference - Load this first for fast context (2KB).
payment-testing
Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal. Covers Stripe test-mode card numbers and their decline codes, the 3DS/SCA challenge flow and its nested-iframe handling in Playwright, test clocks for subscription/billing-cycle…
paddle-sandbox-testing
Test a Paddle integration end-to-end using the sandbox environment, test cards, the webhook simulator, and local tunnels — without taking real money.
spree-testing
Use when the user is writing or running automated tests for a Spree app — model specs, controller specs, API integration tests, admin feature specs, factories, fixtures. Covers RSpec + Factory Bot + Capybara (Spree's stack — NOT Minitest + fixtures), the spreedevtools gem, pulling in Spree's own factories, the shared…