Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add zuora/zuora-coding-agent/plugin install 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-is-migration-design)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-is-migration-design"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-is-migration-design.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.1 | $0.00023 | $0.02477 |
| Opus 5 | $0.00012 | $0.01239 |
| Sonnet 5 | $0.00005 | $0.00495 |
| Haiku 4.5 | $0.00002 | $0.00248 |
Grade A, and why
zuora-is-migration-design 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 6d 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 — 193 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 producing a Credit Memos / Debit Memos migration plan. This plan guides the migration from legacy invoice adjustments (InvoiceAdjustment, InvoiceItemAdjustment, CreditBalanceAdjustment) to the modern Credit Memo and Debit Memo APIs.
REQUIRED INPUT: Codebase Path
Resolve the codebase path before any analysis:
-
If
$ARGUMENTScontainscodebase=<path>, use that path directly and inform the user:"Analyzing codebase at:
<resolved-path>" -
If no path is provided, run
pwdto get the current working directory, then ask:"No codebase path was provided. I will use the current working directory:
<pwd-result>Is this correct, or would you like to specify a different path? (press Enter to confirm, or type the path)"
STOP. Wait for the user to confirm or provide a path before continuing.
Do NOT proceed with any analysis until the path is confirmed.
Input
The user's migration context and codebase path: $ARGUMENTS
Expected format: codebase=/path/to/billing-client or codebase=/path/to/billing-client context:tenant is production with 500 accounts
Tool routing
Use local code search and bundled IS references for code inventory, legacy API detection, mapping tables, and migration-plan structure. Use mcp__zuora-mcp__zuora_codegen for API details and model requirements, mcp__zuora-mcp__query_objects / mcp__zuora-mcp__get_account_summary for tenant state, and mcp__zuora-mcp__ask_zuora only when a specific IS capability, prerequisite, or accounting-semantics question remains unresolved after those sources.
Workflow
When unsure about any aspect of the migration analysis, do NOT guess — list the uncertain items and ask the user before proceeding.
Step 1: Assess current state
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.
- 6d ago First seen · 193 lines · 23 tokens per session scan A c769d5956981
zuora-is-migration-design is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 2,477 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
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
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
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
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.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.