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/zuora/zuora-coding-agentWrote 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/zuora/zuora-coding-agent/zuora-coding-agent)<a href="https://agentmods.dev/rules/zuora/zuora-coding-agent/zuora-coding-agent"><img src="https://agentmods.dev/badge/rules/zuora/zuora-coding-agent/zuora-coding-agent/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/rules/zuora/zuora-coding-agent/zuora-coding-agent"><img src="https://agentmods.dev/badge/rules/zuora/zuora-coding-agent/zuora-coding-agent.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.01839 | $0.01839 |
| Opus 5.5 | $0.00736 | $0.00736 |
| Sonnet 5.5 | $0.00368 | $0.00368 |
| Haiku 4.5 | $0.00184 | $0.00184 |
Grade A, and why
zuora-coding-agent 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When working on Zuora-related tasks, use the zuora-mcp server for authoritative API specs, metadata, code generation, and product knowledge. All commands use the /zuora- prefix.
Available commands
/zuora-api-design— Propose Zuora API approach for a business requirement/zuora-api-build— Generate integration code using the selected APIs/zuora-workflow-design— Design a Zuora Workflow-based solution/zuora-workflow-build— Implement workflow assets or related code/config/zuora-is-migration-design— IS migration strategy, mappings, phases, and risks/zuora-is-migration-build— IS migration implementation artifacts/zuora-order-migration-design— Order migration design, sequencing, and edge-case analysis/zuora-order-migration-build— Order migration implementation artifacts/zuora-meter-design— Design a Zuora meter topology and operator configuration/zuora-meter-build— Compose and lint importable Zuora meter JSON/zuora-dynamic-pricing-design— Design a Commerce Catalog setup with dynamic pricing/zuora-dynamic-pricing-build— Execute the dynamic pricing setup on the tenant/zuora-validate— Validate code/payloads against Zuora patterns/zuora-review— Review work for Zuora best practices/zuora-cpq-apex-design— Design legacy CPQ Apex, Visualforce, Component Library, zQuoteUtil, controller extension, or plugin-interface customizations/zuora-cpq-apex-build— Generate CPQ Apex, Visualforce, Component Library, zQuoteUtil, controller extension, or plugin-interface artifacts into a Salesforce DX repo/zuora-cpq-js-design— Design Quote Studio or CPQ X JavaScript extensibility using supported hooks, events, quote state, and ZQFClient patterns/zuora-cpq-js-build— Generate Quote Studio or CPQ X LWC headless/sidebar components and registration notes into a Salesforce DX repo/zuora-cpq-migration-design— Map or modernize legacy CPQ customizations to Quote Studio hooks/events/zuora-cpq-validate— Validate CPQ Apex, Visualforce, LWC hooks/events, quote-state usage, ZQFClient usage, and global Apex methods/zuora-cpq-review— Review CPQ Apex, Visualforce, Quote Studio LWC, hook/event usage, registration, tests, and maintainability/zuora-uat-design— Extract TR matrix from SDDs (design/testmatrix/)/zuora-uat-build— Build test plan, API scripts, and UI docs for scoped features/zuora-uat-run— Execute API and UI tests with mark-driven verify gate/zuora-html-template-designer— Design and generate Zuora invoice, credit memo, and debit memo HTML templates from prompts and PDFs
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.
- 1mo ago Changed · +12 lines · +356 tokens per session f0e17224b82f
- 2mo ago First seen · 77 lines · 1,483 tokens per session scan A 9ccf03fe53a8
zuora-coding-agent is a cursor rule published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,839 tokens to every session, about $0.0074 per session on Opus 5.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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.