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 JohnWayneeee/casely-qa-skill --skill caselygit clone --depth 1 https://github.com/JohnWayneeee/casely-qa-skillWrote 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/johnwayneeee/casely-qa-skill/casely)<a href="https://agentmods.dev/skills/johnwayneeee/casely-qa-skill/casely"><img src="https://agentmods.dev/badge/skills/johnwayneeee/casely-qa-skill/casely/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/skills/johnwayneeee/casely-qa-skill/casely"><img src="https://agentmods.dev/badge/skills/johnwayneeee/casely-qa-skill/casely.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 63 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 303 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00189 | $0.04993 |
| Opus 5.5 | $0.00076 | $0.01997 |
| Sonnet 5.5 | $0.00038 | $0.00999 |
| Haiku 4.5 | $0.00019 | $0.00499 |
Grade A, and why
casely scanned grade A with 1 finding 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 19d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
method + path, an OpenAPI/Swagger file, `curl` examples, request/response schemas, status How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Casely — QA Test Case Generator
Casely is a Virtual QA Lead. A QA engineer attaches requirement documents (and, ideally, a sample of test cases their team already uses), says what they need, and Casely does the rest in one continuous conversation: it learns the team's format, plans coverage, checks in once before writing anything, then generates test cases and exports them to Excel. When the requirements describe an API, the same run also produces a Postman collection the team can execute — the written cases and the runnable ones stay one suite, not two.
There are no slash commands to run and no project scaffolding to set up by hand. Casely reads attachments the way Claude reads any document — natively. This works the same way in Claude Code, claude.ai (web), and the Claude desktop app.
Why this matters
Manual test case writing accounts for ~40% of a QA engineer's time. Requirements come in fragmented formats (PDF, DOCX, XLSX). Every team has its own column structure, naming conventions, and writing style. Casely solves this by:
- Reading requirement documents directly — no separate parsing step or extra dependency.
- Extracting formal style rules from the team's own example test cases.
- Pausing on a concrete test plan for approval before writing a single test case.
- Applying real test design technique instead of restating the requirements as cases.
- Exporting to one Excel file that a TMS can import in a single pass.
- Turning API-level cases into a Postman collection with every environment-specific value — base URL, tokens, ids — pulled out into variables, so the same file runs against dev, staging, or CI without an edit.
How a conversation with Casely goes
There is no command to type. The user attaches files and says what they need, in any order, in one message or several:
"Here are the requirements for the Payments module and a couple of example test cases my team writes. Give me test cases for the refund flow."
Casely then works through five phases inside that same conversation. Phases 1–2 and 4–5 run without asking for permission at every step; Phase 3 (the test plan) always stops and waits for explicit approval before anything is generated.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · -3 lines · -44 tokens per session 55c2c436676e
- 1mo ago Changed · +78 lines · +74 tokens per session 11d56ef55d7d
- 1mo ago Changed · +60 lines · +92 tokens per session de29bdccf5d8
- 1mo ago First seen · 232 lines · 67 tokens per session scan A 6df406d42897
casely is a skill published in the GitHub repository JohnWayneeee/casely-qa-skill (11 stars, last pushed 19d ago), licensed MIT. It adds 189 tokens to every session and 4,993 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-qa-authoring
Create, edit, validate, and run Agent QA tests, suites, and hooks through MCP or CLI while preserving canonical IDs and schema contracts.
agent-evaluation-reporting
Use when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.
agent-evaluation
Evaluate agent behavior with versioned cases and explicit verifiers. Use when comparing agent or prompt changes, reproducing failures, or running agent regression tests.
quinn
Proves the system works by writing and executing comprehensive test suites.
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.