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-apinpx skills add zuora/zuora-coding-agent --skill execute-apigit 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.00015 | $0.00325 |
| Opus 5 | $0.00008 | $0.00162 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
zuora-uat-execute-api 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 API test (internal)
Tenant resolution
GIT_ROOT=$(git rev-parse --show-toplevel)
eval "$(python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/tenant_resolve.py" \
--git-root "$GIT_ROOT" --environment <environment> 2>&1 | grep '^export')"
export CLEANUP_DEBUG_FILES=false
Config paths: <uat-root>/execution/config/ (default <git-root>/uat/execution/config/).
Ensure $UAT_ROOT/execution/tests/test_utils/ has shipped helpers. Copy any missing files from ${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/tests/test_utils/ (at minimum debug_utils.py, api_client.py, repo_paths.py, uat_root.py).
Run
source "$GIT_ROOT/.venv/bin/activate"
cd "$UAT_ROOT/execution"
python -m pytest "<resolved_api_script>" -v --tb=short \
--junitxml=reports/junit_tr<n>.xml
Resolve script via repo_paths.resolve_api_test_script_path(feature, tr_index).
Outputs
execution/debugging/*.log— for UI stepsexecution/reports/junit*.xml
References
${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/docs/DEBUGGING_MECHANISM_GUIDE.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.
- yesterday First seen · 40 lines · 15 tokens per session scan A a5cab65e1543
zuora-uat-execute-api is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 15 tokens to every session and 325 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…