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/run-featurenpx skills add zuora/zuora-coding-agent --skill run-featuregit 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.00021 | $0.00805 |
| Opus 5 | $0.00010 | $0.00402 |
| Sonnet 5 | $0.00004 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
zuora-uat-run-feature 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 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.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run feature worker (internal)
Inputs: feature, optional tr_filter, verify (auto|true|false), environment, max_fix_retries.
Startup (required, once per feature)
Ensure a canonical verification manifest exists before any TR work:
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" ensure-manifest \
--git-root "$GIT_ROOT" \
--feature "<feature>"
# When tr_filter is set, append --tr N for each TR in scope
Resolve scenario dir: $UAT_ROOT/execution/tests/test_scenarios/test_<feature>/ (via repo_paths.resolve_feature_scenario_dir).
Per-TR verify decision
verify |
Behavior |
|---|---|
false |
Execute directly; no fix/review |
true |
Always run verify segment first |
auto |
Run verify when mark missing, verified: false, or artifact_revision stale |
Check stale marks:
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" should-verify \
--scenario-dir "<scenario_dir>" --tr <n> --git-root "$GIT_ROOT" --feature "<feature>"
Exit 0 → run verify; exit 1 → skip verify.
Per TR in scope
- Verify gate (when applicable) —
verify/SKILL.md. On failure: skip execute for this TR. - Execute API —
execute-api/SKILL.md - Hybrid handoff (required after API pass) — run:
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/hybrid_tr_prepare.py" \
--git-root "$GIT_ROOT" \
--feature "<feature>" \
--tr <n> \
--environment "<environment>"
execute_ui |
Action |
|---|---|
true |
MUST run execute-ui/SKILL.md using variables, ui_steps_path, and debug_log from script output. Do not return worker JSON until UI completes or retries are exhausted. |
false |
Record skip reason in worker JSON (execution.TRn.ui=skipped, execution.TRn.reason=<skip_reason>). Call record-ui-result with --status skipped --reason "<skip_reason>". |
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 · 89 lines · 21 tokens per session scan A e5973f96912b
zuora-uat-run-feature is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 16d ago), licensed MIT. It adds 21 tokens to every session and 805 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…
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.
agui-dotnet-cross-language-tests
Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…
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.
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…
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.