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.
git clone --depth 1 https://github.com/hominhtuong/qa-claude-pluginsWrote 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/commands/hominhtuong/qa-claude-plugins/gen-testcases)<a href="https://agentmods.dev/commands/hominhtuong/qa-claude-plugins/gen-testcases"><img src="https://agentmods.dev/badge/commands/hominhtuong/qa-claude-plugins/gen-testcases/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/hominhtuong/qa-claude-plugins/gen-testcases"><img src="https://agentmods.dev/badge/commands/hominhtuong/qa-claude-plugins/gen-testcases.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01325 |
| Opus 5.5 | $0.00014 | $0.00530 |
| Sonnet 5.5 | $0.00007 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
gen-testcases 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 1mo 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.
- 1mo ago First seen · 60 lines · 35 tokens per session scan A 72f420785a52
gen-testcases is a command published in the GitHub repository hominhtuong/qa-claude-plugins (2 stars, last pushed 4mo ago), with no licence file. It adds 35 tokens to every session and 1,325 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
report
Generer des rapports QA Recette a partir des donnees de session.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
plugin-commands
:::info This document covers all build, test, and smoke commands for eIsland native plugins. Windows plugins live under plugins/windows/; macOS helpers live under plugins/macos/. Each plugin has its own package.json with independent scripts. ::.
add-entry
Command "add-entry" from gosha70/code-copilot-team, covering /add-entry, procedure and refuse to merge if.
Qa
All of QA in one command — builds and maintains the Excel QA workbook (strategy, every module's test cases, role matrix, data rules, findings, run history with when/where each case passed) for the whole application, chosen modules or one feature, derived from the code first and a URL second; runs the cases with a hard…
validate-glossary
A read-only checker for a glossary, which is a shared list defining terms and field names. It checks whether terms are unique and whether the glossary agrees with requirements, database designs, interfaces, and prototypes.