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 skills/zuora/zuora-coding-agent/zuora-api-designnpx skills add zuora/zuora-coding-agent --skill zuora-api-designgit clone --depth 1 https://github.com/zuora/zuora-coding-agentWhat 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 | $0.00017 | $0.00833 |
| Opus 5 | $0.00009 | $0.00417 |
| Sonnet 5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
zuora-api-design 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 3d 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.
1. `code_guidance` with language (default to `curl` if unknown) — understand SDK capabilities How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex-only path resolution: When an instruction refers to ${CLAUDE_PLUGIN_ROOT}, treat it as the root of this installed plugin. In Codex, resolve that root as the ancestor directory containing skills/, references/, and .codex-plugin/.
You are designing a Zuora API integration approach. The user has described a business requirement. Your job is to propose which Zuora APIs, objects, and patterns to use — NOT to generate code yet.
Input
The user's business requirement: $ARGUMENTS
Tool routing
Use mcp__zuora-mcp__zuora_codegen for endpoint discovery, request/response schemas, fields, enum values, SDK method details, and API-specific constraints. Use bundled references for integration patterns and general best practices. Use mcp__zuora-mcp__ask_zuora only if a product-behavior or business-process question remains after those sources are checked.
Workflow
Step 1: Clarify the requirement
If the user's description is ambiguous, ask targeted questions:
- What business outcome are they trying to achieve?
- What system is calling Zuora (backend service, frontend, batch job)?
- What Zuora objects are involved (accounts, subscriptions, invoices, payments)?
- What is the expected data volume and frequency?
- What programming language will be used?
Step 2: Discover relevant APIs
Call mcp__zuora-mcp__zuora_codegen in this order:
code_guidancewith language (default tocurlif unknown) — understand SDK capabilitieslist_api_classes— find relevant API groupsget_class_apisfor the most relevant class(es) — see available endpointsget_api_detailsfor the most relevant endpoint(s) — get parameters, request/response shapes
Step 3: Clarify domain questions
Call mcp__zuora-mcp__ask_zuora for unresolved product-level questions about Zuora Billing, Revenue, CPQ, or Payments behavior. Prefer checking endpoint specs (Step 2) and reference patterns (Step 5) first when they are likely to have the answer, but don't delay if the question is clearly qualitative. Skip this step when specs and references are sufficient.
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.
- 3d ago First seen · 66 lines · 17 tokens per session scan A a4cc9924fb34
zuora-api-design is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 17d ago), licensed MIT. It adds 17 tokens to every session and 833 once invoked, about $0.0001 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
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.
southwest
Search Southwest Airlines fares and points pricing via Patchright browser automation. SW is not in any GDS or API. Covers all fare classes, Companion Pass value, and fare drop monitoring.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
kraken-subaccount-ops
Create and manage subaccounts with inter-account transfers.
equity-research
撰写机构级个股投资研究报告（二级市场深度研究）。Use whenever the user wants to research, analyze, or value a specific publicly-traded stock — e.g. "研究/分析一下某只股票（公司名或代码）"、"帮我看看 NVDA 值不值得买"、"给某只股票写一份投研报告/研报"、"is this stock a buy / overvalued / fairly valued"，或针对某个具名上市公司询问 估值/护城河/财报/目标价/多空逻辑/投资建议（valuation, moat, fundamentals, fair value, price…