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-buildnpx skills add zuora/zuora-coding-agent --skill zuora-api-buildgit 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/skills/zuora/zuora-coding-agent/zuora-api-build)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-api-build"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-api-build.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 | $0.00016 | $0.01216 |
| Opus 5 | $0.00008 | $0.00608 |
| Sonnet 5 | $0.00003 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
zuora-api-build 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.
Identify the target language (Java, Python, Node.js, C#, curl). If not specified, ask the user. Understand what APIs and operations are needed. How it starts
The opening of the file, as written. The whole thing — 86 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 generating Zuora integration code. The user has either already run /zuora-api-design or is describing what they want to build.
Input
The user's request: $ARGUMENTS
Tool routing
This build skill depends on mcp__zuora-mcp__zuora_codegen for API specs, model fields, enum values, SDK idioms, and code rules. Do not use generic product knowledge for code generation details. mcp__zuora-mcp__ask_zuora is allowed only as a fallback for a specific product-behavior question that remains after codegen and references are checked; include the exact uncertainty and sources already checked.
Workflow
Step 1: Determine language and scope
Identify the target language (Java, Python, Node.js, C#, curl). If not specified, ask the user. Understand what APIs and operations are needed.
Step 2: Follow the mandatory codegen workflow
This sequence is critical — call mcp__zuora-mcp__zuora_codegen in this exact order:
code_guidancewith the target language — get SDK setup instructions and workflow guidance. This MUST be called first.list_api_classes— if the right API class is unclear, list all available classes to find the right one.get_class_apis— for the relevant class(es), get all available API methods.get_api_details— for each endpoint you will use, get method signature, parameters, request/response models.get_model_details— for ALL request and response models you will use. This is mandatory to get actual field names, types, and enum values. Call this for each model class. For complex field types, recursively callget_model_details(fieldTypeName).code_rules— get language-specific coding rules. This MUST be called before presenting code to the user.
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 · 86 lines · 16 tokens per session scan A 627b2f0c7895
zuora-api-build is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 1,216 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…