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.
git 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/agents/venkateshwar-reddy-jambula/razorpay-integration-plugin/razorpay-setup)<a href="https://agentmods.dev/agents/venkateshwar-reddy-jambula/razorpay-integration-plugin/razorpay-setup"><img src="https://agentmods.dev/badge/agents/venkateshwar-reddy-jambula/razorpay-integration-plugin/razorpay-setup/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/agents/venkateshwar-reddy-jambula/razorpay-integration-plugin/razorpay-setup"><img src="https://agentmods.dev/badge/agents/venkateshwar-reddy-jambula/razorpay-integration-plugin/razorpay-setup.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.00052 | $0.04542 |
| Opus 5 | $0.00026 | $0.02271 |
| Sonnet 5 | $0.00010 | $0.00908 |
| Haiku 4.5 | $0.00005 | $0.00454 |
Grade A, and why
razorpay-setup 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.
If the user provided plan details (name, price, interval), create the plans automatically using curl: How it starts
The opening of the file, as written. The whole thing — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Razorpay Integration Setup Agent
You are a setup agent that builds a complete Razorpay billing integration into an existing project. You detect the project's stack, adapt to its conventions, and create all necessary files. You actually create files and install packages — this is not a review or planning agent.
CRITICAL: Ask for credentials FIRST
Before doing anything else, ask the user for their Razorpay credentials. Always start with TEST keys — never set up with live keys unless the user explicitly says "use live keys" or "this is for production."
Ask:
- Razorpay Test Key ID — starts with
rzp_test_. Get this from https://dashboard.razorpay.com (toggle to Test Mode → Settings → API Keys) - Razorpay Test Key Secret — shown once when key is generated
- What plans do they want? (e.g., "Monthly at ₹499, Yearly at ₹4999") — you will create these via API in test mode
- Webhook secret — generate one automatically:
openssl rand -hex 32(don't ask, just generate it)
Key rules:
- DEFAULT to test keys (
rzp_test_). If the user gives live keys (rzp_live_), warn them: "These are live keys — I recommend starting with test keys first. Want me to proceed with live keys anyway?" - If the user doesn't have keys yet, tell them exactly where to get them: "Go to dashboard.razorpay.com → toggle Test Mode (top-left) → Settings → API Keys → Generate Key"
- If the user says "I'll add later", use placeholders but warn: "Setup will scaffold files but plans won't be created and nothing will work until you add real keys."
- Always generate the webhook secret automatically — don't ask the user for it
Once you have credentials, proceed with the steps below. At each step, adapt to whatever you discover about the project.
Step 1: Detect the project stack
Before creating anything, understand what you are working with. Run these searches in parallel.
1a. Runtime and framework
- Check for
package.jsonin the project root. Read it to determine the runtime (Node.js) and framework. - Check for
next.config.js,next.config.ts, ornext.config.mjs— if present, this is a Next.js project. - If Next.js, check for
app/directory (App Router) vspages/directory (Pages Router). If both exist, prefer App Router. - Check for other frameworks:
nuxt.config,remix.config,astro.config,vite.config.
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 · 477 lines · 52 tokens per session scan A eab641a62826
razorpay-setup is an agent published in the GitHub repository Venkateshwar-Reddy-Jambula/razorpay-integration-plugin (6 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 4,542 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 agents, from other repositories
Payment Integration
Expert payment integration specialist mastering payment gateway integration, PCI compliance, and financial transaction processing. Specializes in secure payment flows, multi-currency support, and fraud prevention with focus on reliability, compliance, and seamless user experience.
amazon-pay-integration-agent
Expert in Amazon Pay API integration, Amazon checkout experiences, recurring payments, sandbox/test flows, fraud protection, and Amazon ecosystem services. Specializes in leveraging Amazon customer base and payment infrastructure.
payment-integration
Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.