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 skills add Xuzan9396/plugin_claude --skill xz-casesgit clone --depth 1 https://github.com/Xuzan9396/plugin_claudeWrote 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/xuzan9396/plugin_claude/xz-cases)<a href="https://agentmods.dev/skills/xuzan9396/plugin_claude/xz-cases"><img src="https://agentmods.dev/badge/skills/xuzan9396/plugin_claude/xz-cases.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.00066 | $0.03324 |
| Opus 5 | $0.00033 | $0.01662 |
| Sonnet 5 | $0.00013 | $0.00665 |
| Haiku 4.5 | $0.00007 | $0.00332 |
Grade A, and why
xz-cases 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago Changed · -97 lines 25c1d4400b5f
- 6d ago First seen · 299 lines · 66 tokens per session scan A 178c2b29b49f
xz-cases is a skill published in the GitHub repository Xuzan9396/plugin_claude (6 stars, last pushed 4d ago), with no licence file. It adds 66 tokens to every session and 3,324 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
spreadsheet-create-verify-gate
Create or edit Excel workbooks with openpyxl-specific pitfall handling, anchored preflight audit, and deterministic post-write proof that every criterion is satisfied.
spreadsheet-direct-verification
Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent.
spreadsheet-proof-gate-merged-fedf41-merged
The derived skill is complete and provides a meaningful enhancement.
define-data
Standalone Phase 4 of SAP UI testing. Authors one tests/ /test-cases/TC-XXX.data.md requirement spec per case marked dataRequired: yes — choosing the narrowest correct source (sql/static/generated/seeded), and generating upload fixtures in the EXACT file format the program parses (xlsx vs csv). Validates that every…
postman-test-implementation
Converts an approved company-format testcase workbook (from api-test-design + company-testcase-format) into one Postman collection and one Postman environment, using conventions learned from real company artifacts and this project's src/postman builders. Does not execute anything and does not decide what to test.
company-testcase-format
Formats scenarios produced by api-test-design into the company's real QA testcase conventions (spreadsheet columns, TCID scheme, Postman naming/scripting), learned from actual SDA V2 reference artifacts and kept service-agnostic — never copies SDA's API fields/values into another service's testcase sheet.