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-designnpx skills add zuora/zuora-coding-agent --skill zuora-uat-designgit 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-design)<a href="https://agentmods.dev/skills/zuora/zuora-coding-agent/zuora-uat-design"><img src="https://agentmods.dev/badge/skills/zuora/zuora-coding-agent/zuora-uat-design.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.00027 | $0.00661 |
| Opus 5 | $0.00014 | $0.00331 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
zuora-uat-design 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.
Extract Zuora Billing use cases from SDDs into <uat-root>/design/testmatrix/. No tenant access.
Input
$ARGUMENTS
| Parameter | Default | Notes |
|---|---|---|
project_name |
(omit) | When set, {project}_{System}_TRs.md. When omitted, {Feature}_TRs.md |
sdd_path |
docs/sdd/ |
Relative to git root (not uat/) |
analysis_mode |
full |
incremental requires target_sdd_file |
tr_scope |
focused |
TR count caps |
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'])")
Default UAT root: $GIT_ROOT/uat/. Override with UAT_ROOT or .zuora-uat.yaml (root: . for dedicated test repos).
Step 2: Scaffold if needed
If $UAT_ROOT/design/testmatrix/ is missing:
mkdir -p "$GIT_ROOT/uat"
cp -r "${CLAUDE_PLUGIN_ROOT}/templates/uat-test-starter/uat/"* "$GIT_ROOT/uat/"
cp "${CLAUDE_PLUGIN_ROOT}/templates/uat-test-starter/.zuora-uat.yaml" "$GIT_ROOT/.zuora-uat.yaml"
Step 3: Run design extraction
Read ${CLAUDE_PLUGIN_ROOT}/skills/zuora-uat/design/SKILL.md. Write TR files under $UAT_ROOT/design/testmatrix/.
Step 4: Summarize
Report UAT root, files written, TR counts, caps applied.
References
${CLAUDE_PLUGIN_ROOT}/references/uat-test/design/README.md${CLAUDE_PLUGIN_ROOT}/skills/zuora-uat/design/SKILL.md
MCP substitution
Use mcp__zuora-mcp__zuora_codegen for API specs; mcp__zuora-mcp__ask_zuora only for unresolved product-behavior 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.
- 5d ago First seen · 61 lines · 27 tokens per session scan A 38acb2010f3a
zuora-uat-design is a skill published in the GitHub repository zuora/zuora-coding-agent (2 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 661 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…