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-contextnpx skills add zuora/zuora-coding-agent --skill zuora-contextgit 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.00124 | $0.02303 |
| Opus 5 | $0.00062 | $0.01151 |
| Sonnet 5 | $0.00025 | $0.00461 |
| Haiku 4.5 | $0.00012 | $0.00230 |
Grade B, and why
zuora-context scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Claude Code:** `~/.claude/settings.json` under the `"mcpServers"` key How it starts
The opening of the file, as written. The whole thing — 141 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/.
Zuora Context
MCP health check
Before doing any work that requires MCP tools, check whether any mcp__zuora-mcp__* tool appears in your available tools list. If no mcp__zuora-mcp__ tools are listed, the MCP server is not registered — immediately stop and show the user this setup guide rather than proceeding silently with degraded capabilities:
zuora-mcp is not configured. This plugin requires the zuora-mcp MCP server to access Zuora tenant data, API specs, and operational tools.
Add the following to your MCP configuration:
{
"mcpServers": {
"zuora-mcp": {
"command": "npx",
"args": ["-y", "zuora-mcp@latest"],
"env": {
"ZUORA_BASE_URL": "<your-base-url>",
"ZUORA_CLIENT_ID": "<your-client-id>",
"ZUORA_CLIENT_SECRET": "<your-client-secret>"
}
}
}
}
Where to add it:
- Claude Code:
~/.claude/settings.jsonunder the"mcpServers"key - Codex (local zip install):
~/.codex/plugins/cache/zuora-devex/zuora-coding-agent/<version>/.mcp.json - Cursor: Settings → MCP → Add server
- Other MCP clients: your client's MCP server config file
ZUORA_BASE_URL by environment:
| Environment | URL |
|---|---|
| US API Sandbox (Cloud 2) | https://apisandbox.zuora.com/mcp |
| US NA Sandbox | https://sandbox.na.zuora.com/mcp |
| US Central Sandbox | https://test.zuora.com/mcp |
| EU Sandbox | https://sandbox.eu.zuora.com/mcp |
| US Production | https://zuora.com/mcp |
| US NA Production | https://na.zuora.com/mcp |
| EU Production | https://eu.zuora.com/mcp |
| AP Production | https://ap.zuora.com/mcp |
The legacy https://rest.*.zuora.com URL format is also accepted for backward compatibility.
Optional environment variables (add to the env block above only if needed):
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 · 141 lines · 124 tokens per session scan B 879ea30639b1
zuora-context is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 16d ago), licensed MIT. It adds 124 tokens to every session and 2,303 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.