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/plannpx skills add zuora/zuora-coding-agent --skill plangit 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.00019 | $0.00529 |
| Opus 5 | $0.00010 | $0.00264 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
zuora-uat-plan 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
Create test plan (internal)
Creates design/testplan/<Feature>_Test_Plan/ with Test_Plan_Overview.md + tr{n}_test_design.md.
Design-only boundary: design/testplan/ must contain only plan documents. Never create ui_steps_tr{n}.md or API test scripts there — those are execution artifacts under execution/tests/test_scenarios/test_<feature>/.
Gap-fill
When force_overwrite=false, only create missing tr{n}_test_design.md. Update overview links for new TRs.
Path resolution
Use execution/tests/test_utils/repo_paths.py from the customer repo (copy any missing files from ${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/tests/test_utils/):
resolve_feature_testplan_dir(feature)resolve_tr_test_design_path(feature, tr_index)testplan_overview_path(feature)resolve_feature_scenario_dir(feature)— for execution-artifact paths in hybrid plan docs
Writing rules
- Overview ≤120 lines: prerequisites, shared API refs, links to per-TR files
- Per-TR file ≤200 lines: Test ID, Summary, UI Test Doc Required (hybrid), Steps, Notes
- Hybrid TRs: mark
UI Test Doc Required: Yes - Hybrid TR cross-reference in
tr{n}_test_design.md:- Use:
## UI steps (see execution/tests/test_scenarios/test_<feature>/ui_steps_tr{n}.md) - Keep a short inline UI summary in the plan; the full Playwright doc belongs in execution
- Use:
Test_Plan_Overview.mdfor hybrid features must include:Execution artifacts: execution/tests/test_scenarios/test_<feature>/- Artifacts table lists filenames only (e.g.
ui_steps_tr1.md,test_<feature>_tr1_api.py)
References
${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/docs/SHARED_STAGING_TENANT_POLICY.md${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/docs/E2E_TEST_IMPLEMENTATION_GUIDELINE.md
MCP
mcp__zuora-mcp__zuora_codegen for endpoint details; mcp__zuora-mcp__ask_zuora for unresolved UI/navigation questions.
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 · 45 lines · 19 tokens per session scan A a360322ae2fa
zuora-uat-plan is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 19 tokens to every session and 529 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…