zuora-coding-agent

Persistent working rules for development tasks involving Zuora, a platform for subscription billing, invoicing, payments, and revenue management. It defines the available Zuora commands and their intended order of use.

In plain words
What is it for?
Use it whenever a task involves Zuora APIs, billing, payments, CPQ, subscriptions, workflows, migrations, meters, pricing, tenant configuration, or validation.
Why use it?
It keeps Zuora work consistent by directing the coding agent to authoritative API specifications, metadata, product information, and validation steps.

Cursor rule

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.

agentmods
npx agentmods add rules/zuora/zuora-coding-agent/zuora-coding-agent
Clone the repo
git clone --depth 1 https://github.com/zuora/zuora-coding-agent
Per session 1,483 This file is loaded in full into every session.
When invoked 1,483 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.01483 $0.01483
Opus 5 $0.00741 $0.00741
Sonnet 5 $0.00297 $0.00297
Haiku 4.5 $0.00148 $0.00148

Measured yesterday against content hash 9ccf03fe53a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

rules/zuora-coding-agent.mdc · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 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

Read the full file on GitHub · 77 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. yesterday First seen · 77 lines · 1,483 tokens per session scan A 9ccf03fe53a8

Subscribe to this mod's changes

zuora-coding-agent is a cursor rule published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 1,483 tokens to every session, about $0.0074 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-31.