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 agentmods add rules/razorpay/razorpay-mcp-server/new-tool-from-docsgit clone --depth 1 https://github.com/razorpay/razorpay-mcp-serverWrote 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/rules/razorpay/razorpay-mcp-server/new-tool-from-docs)<a href="https://agentmods.dev/rules/razorpay/razorpay-mcp-server/new-tool-from-docs"><img src="https://agentmods.dev/badge/rules/razorpay/razorpay-mcp-server/new-tool-from-docs.svg" alt="Measured on agentmods" 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.02205 | $0.02205 |
| Opus 5 | $0.01103 | $0.01103 |
| Sonnet 5 | $0.00441 | $0.00441 |
| Haiku 4.5 | $0.00220 | $0.00220 |
Grade A, and why
new-tool-from-docs 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Razorpay Tool Generator
This rule generates tool implementations for the Razorpay MCP server based on API documentation.
Required Format
This rule requires:
- A Razorpay API documentation URL starting with
https://razorpay.com/docs/api/ - The SDK function signature that the tool will call
Example of valid invocation:
@new-tool-from-docs.mdc DOC_LINK: @https://razorpay.com/docs/api/payment-links/create-standard/
SDK_FUNCTION:
func (pl *PaymentLink) Create(data map[string]interface{}, extraHeaders map[string]string) (map[string]interface{}, error) {
url := fmt.Sprintf("/%s%s", constants.VERSION_V1, constants.PaymentLink_URL)
return pl.Request.Post(url, data, extraHeaders)
}
IMPORTANT: If the DOC_LINK or SDK_FUNCTION are missing or in an incorrect format, REFUSE to proceed further.
Implementation Checklist
This checklist MUST be included in the final response to verify all implementation steps are complete. IMPORTANT: Include this unchecked checklist at the END of the implementation, NOT at the beginning.
- Implement tool function based on API docs
- Register tool in tools.go
- Create unit tests with full coverage (positive case, all negative cases, edge cases)
- Update the "Available Tools" section in the main README.md. Make sure the new additions are correctly formatted.
- Double check that we are not repeating any of the Common Issues mentioned below.
- Run linter and fix errors if any (REQUIRED)
- Run tests and fix errors if any (REQUIRED)
COMPLETION CRITERIA:
- The task is considered accomplished only if the checklist and summary are posted.
- Once the task is completed you should stop and give control to the user. You SHOULD NOT infer additional tools to implement.
⚠️ IMMEDIATE ACTION REQUIRED ⚠️
Upon receiving this rule invocation:
- DO NOT ask for user input or confirmation before implementing code
- DO use the
edit_filetool to create/modify the following files:- Primary implementation:
pkg/razorpay/{resource_type}.go - Test implementation:
pkg/razorpay/{resource_type}_test.go - Update toolset registration:
pkg/razorpay/tools.go - Update the README.md
- Primary implementation:
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.
- 6d ago First seen · 262 lines · 2,205 tokens per session scan A 5301d5352bbe
new-tool-from-docs is a cursor rule published in the GitHub repository razorpay/razorpay-mcp-server (230 stars, last pushed 8d ago), licensed MIT. It adds 2,205 tokens to every session, about $0.0110 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
toc-readme
When updating README.md, the table of contents should contain only the second-level headings below it.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
cursor_rules
Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.
validate-design-early
Ask for design approval before implementing 100+ lines.