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-contextnpx skills add zuora/zuora-coding-agent --skill zuora-uat-contextgit 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-context)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-uat-context"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-uat-context.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 | $0.00070 | $0.00542 |
| Opus 5 | $0.00035 | $0.00271 |
| Sonnet 5 | $0.00014 | $0.00108 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
zuora-uat-context 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 4d 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.
Zuora UAT context router
UAT workspace layout
UAT artifacts live under <git-root>/uat/ by default (not repo root) to avoid collisions in mixed repos.
your-repo/
├── .zuora-uat.yaml # root: uat
├── docs/sdd/ # SDDs at git root
└── uat/
├── design/
└── execution/
Dedicated test repos: root: . in .zuora-uat.yaml or UAT_ROOT=.
Registered commands
/zuora-uat-design—$zuora-uat-design/zuora-uat-build—$zuora-uat-build/zuora-uat-run—$zuora-uat-run
Command routing
| User intent | Command |
|---|---|
| Extract TRs from SDDs | /zuora-uat-design |
| Build plan + API + UI docs | /zuora-uat-build |
| Run API + UI tests | /zuora-uat-run |
Typical chain
/zuora-uat-design
/zuora-uat-build features_input=<scope>
/zuora-uat-run features_input=<scope>
Read the matching top-level skill and follow it.
References
Bundled under ${CLAUDE_PLUGIN_ROOT}/references/uat-test/:
design/README.md— UAT workspace layoutexecution/docs/E2E_TEST_IMPLEMENTATION_GUIDELINE.md— API test patternsexecution/docs/DEBUGGING_MECHANISM_GUIDE.md— debug log format (debug_utils.py)execution/docs/UI_TEST_DOC_FORMAT.md/UI_TEST_EXECUTION_GUIDELINE.md— hybrid UI steps
MCP
Use zuora-mcp (zuora_codegen, ask_zuora) per plugin tool-routing policy. UI execution also needs user-configured Playwright MCP.
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.
- 4d ago First seen · 62 lines · 70 tokens per session scan A 54eb91086090
zuora-uat-context is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 542 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…