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-reviewnpx skills add zuora/zuora-coding-agent --skill zuora-reviewgit 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-review)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-review"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-review.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.00011 | $0.00880 |
| Opus 5 | $0.00005 | $0.00440 |
| Sonnet 5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
zuora-review 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 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.
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 — 75 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 reviewing Zuora-related implementation work for best practices, completeness, and correctness. This is broader than /zuora-validate — it evaluates the overall approach, not just individual code correctness.
Input
What to review: $ARGUMENTS
Tool routing
Use local file reads and bundled references for implementation facts and baseline best practices. Use mcp__zuora-mcp__zuora_codegen for SDK/API-specific rules and mcp__zuora-mcp__query_objects only when tenant state matters to the review. Use mcp__zuora-mcp__ask_zuora only for a concrete product-behavior or best-practice judgment that remains unresolved after those sources.
Workflow
Step 1: Understand scope
Read the files or description. Determine what aspects to review:
- API integration code
- Workflow implementation
- Migration plan or scripts
- Product catalog setup
- Template/form design
- Overall architecture and approach
Step 2: Gather Zuora context
Use MCP tools as needed:
mcp__zuora-mcp__ask_zuora— for unresolved product-level best-practice questions; prefer reading the bundled references (Step 3) first when they are likely to have the answer, but call earlier if the question is clearly qualitativemcp__zuora-mcp__zuora_codegenwithcode_rules— for SDK-specific patternsmcp__zuora-mcp__query_objects— to check tenant state if relevant to the review
Step 3: Read reference material
Read the relevant files from ${CLAUDE_PLUGIN_ROOT}/references/:
best-practices.md— always read for general Zuora best practicesapi-integration-patterns.md— for API integration reviewsworkflow-patterns.md— for workflow reviewsis-migration-patterns.md— for IS migration reviewsorder-migration-patterns.md— for Order API migration reviews
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 Changed 3a6938b21b50
- 5d ago First seen · 75 lines · 11 tokens per session scan A 5633df8599c5
zuora-review is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 880 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…