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/execute-uinpx skills add zuora/zuora-coding-agent --skill execute-uigit 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.00016 | $0.00388 |
| Opus 5 | $0.00008 | $0.00194 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
zuora-uat-execute-ui 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 yesterday.
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.
What it actually says
Execute UI test (internal)
Entry
Prefer starting from hybrid_tr_prepare.py output (called by run-feature after API pytest passes):
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/hybrid_tr_prepare.py" \
--git-root "$GIT_ROOT" \
--feature "<feature>" \
--tr <n> \
--environment "<environment>"
When execute_ui is true, proceed. Otherwise stop and return the skip_reason.
Manual fallback for debug variables:
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/parse_debug_variables.py" \
--git-root "$GIT_ROOT" \
--feature "<feature>" \
--tr <n>
Preconditions
Skip UI with a clear message when any of:
hybrid_tr_prepare.pyreturnsexecute_ui: false- Playwright MCP unavailable
- API pytest failed for this TR (
api_test_passed: false)
Process
- Use
variablesfromhybrid_tr_prepare.py(orparse_debug_variables.py) — do not hand-parse debug logs unless scripts fail - Read
ui_steps_path/ui_steps_tr{n}.md - Execute steps via Playwright MCP tools
- Write report to
execution/reports/ - Capture evidence paths for
record-ui-result
Follow ${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/docs/UI_TEST_EXECUTION_GUIDELINE.md.
MCP
Use user-configured Playwright MCP (not bundled). mcp__zuora-mcp__ask_zuora for unresolved UI behavior only.
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.
- yesterday First seen · 52 lines · 16 tokens per session scan A 0abc97faeb27
zuora-uat-execute-ui is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 388 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
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".