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-uat-build)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-uat-build"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-uat-build.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.00763 |
| Opus 5 | $0.00012 | $0.00381 |
| Sonnet 5 | $0.00005 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
zuora-uat-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 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 — 79 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.
Orchestrator: discover scope → one worker per feature → aggregate. Does not run pytest by default (verify=false).
Input
$ARGUMENTS
Workflow
Step 1: Resolve paths and scaffold
GIT_ROOT=$(git rev-parse --show-toplevel)
UAT_ROOT=$(python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/resolve_uat_root.py" \
--git-root "$GIT_ROOT" | python3 -c "import sys,json; print(json.load(sys.stdin)['uat_root'])")
If $UAT_ROOT/design missing, scaffold per zuora-uat-design Step 2.
Step 2: Discover scope
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/discover_groups.py" \
--git-root "$GIT_ROOT" \
--features-input "<features_input>"
Step 3: Delegate per feature
Pass workers: feature stem, tr_filter, flags, UAT_ROOT, and ${CLAUDE_PLUGIN_ROOT}/skills/zuora-uat/generate-feature/SKILL.md.
Multiple features: sequential sub-agents. Single feature: inline OK.
Collect compact JSON summary only from workers.
Step 3b: Finalize verification marks (required)
After each feature worker completes, always run (do not skip even if the worker JSON already lists verification):
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" finalize-generate \
--git-root "$GIT_ROOT" \
--feature "<feature_stem>" \
--verify "<verify>"
# When the worker had tr_filter, append --tr N for each TR in scope
When verify=false, this writes {"verified": false} for every TR in scope to .uat-verification.json. When verify=true, this is a no-op (the verify segment sets marks on pass/fail).
Validate the manifest (must pass before continuing):
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" validate \
--scenario-dir "$UAT_ROOT/execution/tests/test_scenarios/<scenario_folder>"
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 · 79 lines · 23 tokens per session scan A 5214d409661a
zuora-uat-build is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 763 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.