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-validatenpx skills add zuora/zuora-coding-agent --skill zuora-validategit 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.00018 | $0.00804 |
| Opus 5 | $0.00009 | $0.00402 |
| Sonnet 5 | $0.00004 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
zuora-validate 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 2d 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.
- curl commands or raw API payloads How it starts
The opening of the file, as written. The whole thing — 74 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 validating Zuora-related code, API payloads, or design approaches against known Zuora patterns and best practices.
Input
What to validate: $ARGUMENTS
Tool routing
Use local file reads, bundled references, and mcp__zuora-mcp__zuora_codegen for structured validation of APIs, models, fields, enum values, SDK patterns, and payload shape. Use mcp__zuora-mcp__ask_zuora only when a concrete product-behavior or best-practice judgment remains after those checks.
Workflow
Step 1: Identify what to validate
Read the file or inline content the user provides. Determine the type:
- SDK integration code (Java, Python, Node.js, C#)
- curl commands or raw API payloads
- API design approach
- Workflow configuration
- Migration plan or scripts
Step 2: Check against SDK rules
For code validation, call mcp__zuora-mcp__zuora_codegen:
code_rulesfor the relevant language — get coding rules and patternsget_model_detailsfor models used in the code — verify field names, types, and enum values are correctget_api_detailsfor endpoints used — verify correct HTTP methods, required parameters, and request shapes
Step 3: Check against best practices
Read ${CLAUDE_PLUGIN_ROOT}/references/best-practices.md and check for:
- Authentication: Is OAuth token caching implemented? Are credentials hardcoded?
- Error handling: Are retries with exponential backoff implemented for transient failures (429, 5xx)?
- Pagination: Is cursor-based pagination used for list operations?
- Idempotency: Are create operations guarded with Idempotency-Key headers?
- Rate limiting: Is rate limit handling present?
- Field correctness: Are enum values and field names from actual SDK models (not guessed)?
- Date formats: Are dates in YYYY-MM-DD format?
- Required fields: Are all required fields populated?
- Zuora-Version header: Is it included and pinned to a known version?
- STOP_AND_CONFIRM handling: Are permanent error responses handled without retry?
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.
- 2d ago First seen · 74 lines · 18 tokens per session scan A 9b5c69ce70df
zuora-validate is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 16d ago), licensed MIT. It adds 18 tokens to every session and 804 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.