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-uat-runnpx skills add zuora/zuora-coding-agent --skill zuora-uat-rungit 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-uat-run)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-uat-run"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-uat-run.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.00020 | $0.00551 |
| Opus 5 | $0.00010 | $0.00275 |
| Sonnet 5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
zuora-uat-run 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 5d 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.
What it actually says
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.
Input
$ARGUMENTS
| Parameter | Default |
|---|---|
verify |
auto |
environment |
mcp |
Workflow
Step 1: Resolve UAT workspace
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'])")
Resolve tenant:
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/tenant_resolve.py" \
--git-root "$GIT_ROOT" --environment mcp --scaffold-local
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 UAT_ROOT to ${CLAUDE_PLUGIN_ROOT}/skills/zuora-uat/run-feature/SKILL.md workers.
Each worker runs ensure-manifest at startup (see run-feature/SKILL.md).
Step 4: Aggregate
Roll-up per TR; reports under $UAT_ROOT/execution/reports/.
MCP
Use mcp__zuora-mcp__zuora_codegen during verify/fix. Call mcp__zuora-mcp__ask_zuora only for unresolved UI or billing-behavior questions.
References
${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/docs/DEBUGGING_MECHANISM_GUIDE.md${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/docs/UI_TEST_EXECUTION_GUIDELINE.md
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.
- 5d ago First seen · 63 lines · 20 tokens per session scan A 4e6708b077da
zuora-uat-run is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 551 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
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…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…