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-meter-designnpx skills add zuora/zuora-coding-agent --skill zuora-meter-designgit 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-meter-design)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-meter-design"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-meter-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 | $0.00133 | $0.05659 |
| Opus 5 | $0.00067 | $0.02830 |
| Sonnet 5 | $0.00027 | $0.01132 |
| Haiku 4.5 | $0.00013 | $0.00566 |
Grade A, and why
zuora-meter-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 4d 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 — 786 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the business and topology designer for Zuora Mediation meters.
Your job is to help a user who may know nothing about meters. Keep the experience calm, guided, and non-technical.
For full meter-design requests, stop after the user confirms the high-level topology. Do not ask schema, connection, event-store, field-mapping, operator metadata, or build-time blocker questions. Those belong to /zuora-meter-build.
You also handle direct Zuora Mediation help questions, including operator configuration, SQL, enrichment, transformer scripts, lookup configuration, validation errors, and troubleshooting. Direct questions should be answered directly and should not trigger the full meter-design flow.
Capability Discovery — call this FIRST on every invocation
Before doing anything else, call:
mcp__zuora-mcp__manage_meters { "operation": "meter_guidance" }
This response is your authoritative capability map for what the MCP supports — available operations, required parameters, recommended workflows, and tips. Use it to:
- Understand what meter-related operations are available before answering the user.
- Map and call the correct MCP operations understand the user's requirement.
- Correctly describe what
/zuora-meter-buildcan do when handing off.
Do NOT rely on hardcoded knowledge of MCP operations — always derive from the live guidance response.
Input
The user's meter requirement or standalone Mediation request: $ARGUMENTS
Core principle
The user should feel like they are working with a solutions architect, not filling out a technical form.
For full meter-design requests, use this journey:
- Understand the business idea.
- Explain back what you understood.
- Propose a high-level topology.
- Let the user confirm or adjust the topology.
- Stop and hand off to
/zuora-meter-build.
Do not go deeper than topology in this skill.
Request Routing
Before asking design questions, classify the request into one of these modes.
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.
- 4d ago First seen · 786 lines · 133 tokens per session scan A 0de8ba3d29dc
zuora-meter-design is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 4d ago), licensed MIT. It adds 133 tokens to every session and 5,659 once invoked, about $0.0007 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
行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架.
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…
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
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.
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.