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-workflow-designnpx skills add zuora/zuora-coding-agent --skill zuora-workflow-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-workflow-design)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-workflow-design"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-workflow-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.00013 | $0.05978 |
| Opus 5 | $0.00006 | $0.02989 |
| Sonnet 5 | $0.00003 | $0.01196 |
| Haiku 4.5 | $0.00001 | $0.00598 |
Grade A, and why
zuora-workflow-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 3d 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 — 238 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 designing a Zuora Workflow-based automation solution. The user has described a business process they want to automate.
Design output is not an import artifact. Do not emit partial Workflow import JSON, abbreviated JSON, ellipsized task arrays, or "representative" JSON that could be copied into Workflow. If the user asks for JSON, either proceed with the zuora-workflow-build skill or explicitly hand off to it so the complete .workflow.json artifact can be composed, linted, and delivered.
Input
The user's automation requirement: $ARGUMENTS
Workflow
Step 1: Understand the business process
If the requirement is unclear, ask targeted questions:
- What business process needs automation?
- What Zuora objects are involved?
- What external systems need integration (CRM, ERP, notification services)?
- What is the expected volume and frequency?
- What should happen on failure?
Step 1a: Clarify the trigger style
Pick one or more trigger modes and confirm with the user if ambiguous. Each mode maps to one boolean flag on workflow, and Workflow supports multiple flags on a single setup:
- Event-triggered (
event_trigger) — fires on a Zuora business event (e.g.,InvoicePosted,PaymentProcessed, or tenant-custom events). Requiresparameters.event_triggers+parameters.event_parameters. - Scheduled (
scheduled_trigger) — cron-based recurrence. Requiresinterval(cron) +timezone(RailsActiveSupport::TimeZonefriendly name, e.g."Pacific Time (US & Canada)"). Do not use bare IANA names like"America/Los_Angeles"in the final JSON. - Callout-triggered (
callout_trigger) — external system POSTs to the workflow's callout URL. - On-demand (
ondemand_trigger) — user runs it manually from the Workflow UI or via API.
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.
- 3d ago First seen · 238 lines · 13 tokens per session scan A a49687835650
zuora-workflow-design is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 5,978 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.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…