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-tenant-config-build)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-tenant-config-build"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-tenant-config-build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-tenant-config-build"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-tenant-config-build.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.02944 |
| Opus 5 | $0.00010 | $0.01472 |
| Sonnet 5 | $0.00004 | $0.00589 |
| Haiku 4.5 | $0.00002 | $0.00294 |
Grade A, and why
zuora-tenant-config-build 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 9d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are applying Zuora tenant configuration changes directly to the tenant using MCP tools. This skill executes — it does NOT generate code.
How manage_settings works under the hood
All three operations go through the Zuora Settings batch API (POST /settings/batch-requests):
| Operation | HTTP method | When to use |
|---|---|---|
list_setting_keys |
— | Discover available paths — fall back to this only if a path is not found in settings-schema.json |
get_settings |
GET | Read current value before any update |
update_settings |
PUT | Update an existing setting or collection item |
create_settings |
POST | Create a new collection item (e.g., new payment term) |
Key mechanics:
settingValueJsonmust always be a JSON object{...}, never a bare array[...]. The tool rejects arrays immediately.- For per-ID collection updates, include the item ID in
settingKey(e.g.,/payment-terms/abc123), not in the payload body. - For full array replace settings (e.g.,
/currencies), a single PUT replaces the entire collection — include all items, both changed and unchanged. - For new collection items (e.g., a payment term that doesn't exist yet), use
create_settingswith the base collection key (e.g.,/payment-terms). - Payment gateways are an exception — gateway creation requires provisioning outside this tool; only updates are supported via
update_settings.
Always check "success": true in the response before moving to the next operation.
Input
The user's configuration plan or instructions: $ARGUMENTS
The plan from /zuora-tenant-config-design carries values in UI terms (field_key + option strings from settings-fields.json). Your job is to translate those into API payloads using settings-field-mappings.json, then apply them via manage_settings.
If no design plan exists and the request involves more than two settings, recommend running /zuora-tenant-config-design first.
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.
- 9d ago First seen · 270 lines · 20 tokens per session scan A 86239076ce3d
zuora-tenant-config-build is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 2,944 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.