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 latestaiagents/agent-skills --skill test-case-designgit clone --depth 1 https://github.com/latestaiagents/agent-skillsWrote 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/latestaiagents/agent-skills/test-case-design)<a href="https://agentmods.dev/skills/latestaiagents/agent-skills/test-case-design"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-skills/test-case-design/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/latestaiagents/agent-skills/test-case-design"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-skills/test-case-design.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.00057 | $0.02005 |
| Opus 5 | $0.00028 | $0.01002 |
| Sonnet 5 | $0.00011 | $0.00401 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
test-case-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.
How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Case Design
Write comprehensive, maintainable test cases that catch bugs early.
When to Use
- Writing test cases for new features
- Improving test coverage
- Creating regression test suites
- Documenting test scenarios
- Training new QA team members
Test Case Structure
Standard Format
## Test Case: TC-[ID]
**Title:** [Clear, action-oriented title]
**Priority:** P0 / P1 / P2 / P3
**Type:** Functional / Regression / Smoke / Edge Case
### Preconditions
- [System state required before test]
- [User state/data required]
### Test Data
- [Specific data needed]
### Steps
| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | [Do this] | [See this] |
| 2 | [Do that] | [Observe that] |
| 3 | [Verify] | [Confirm] |
### Postconditions
- [Expected system state after test]
### Notes
- [Edge cases, known issues, etc.]
Example Test Case
## Test Case: TC-LOGIN-001
**Title:** Successful login with valid credentials
**Priority:** P0
**Type:** Smoke
### Preconditions
- User account exists with email: [email protected]
- User is not currently logged in
- Application is accessible
### Test Data
- Email: [email protected]
- Password: ValidPassword123!
### Steps
| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | Navigate to /login | Login page displays with email and password fields |
| 2 | Enter email "[email protected]" | Email field populated |
| 3 | Enter password "ValidPassword123!" | Password field shows masked input |
| 4 | Click "Sign In" button | Loading indicator appears |
| 5 | Wait for redirect | User redirected to /dashboard |
### Postconditions
- User is logged in
- Session cookie is set
- Welcome message shows username
### Notes
- Also verify with uppercase email variant
- Test "Remember me" checkbox separately
BDD/Gherkin Format
Feature File
# features/login.feature
Feature: User Login
As a registered user
I want to log into my account
So that I can access my personalized content
Background:
Given I am on the login page
And I have a valid account
@smoke @p0
Scenario: Successful login with valid credentials
When I enter my email "[email protected]"
And I enter my password "ValidPassword123"
And I click the "Sign In" button
Then I should be redirected to the dashboard
And I should see "Welcome back" message
@p1
Scenario: Login fails with incorrect password
When I enter my email "[email protected]"
And I enter my password "WrongPassword"
And I click the "Sign In" button
Then I should see an error message "Invalid credentials"
And I should remain on the login page
@p1
Scenario Outline: Login validation errors
When I enter my email "<email>"
And I enter my password "<password>"
And I click the "Sign In" button
Then I should see an error message "<error>"
Examples:
| email | password | error |
| | pass123 | Email is required |
| invalid-email | pass123 | Invalid email format |
| [email protected] | | Password is required |
| [email protected] | short | Password too short |
@p2
Scenario: Account locked after multiple failed attempts
Given I have failed login 4 times
When I enter my email "[email protected]"
And I enter my password "WrongPassword"
And I click the "Sign In" button
Then I should see "Account locked" message
And I should see "Try again in 15 minutes"
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 · 321 lines · 57 tokens per session scan A 0b641aed02a6
test-case-design is a skill published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 2,005 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-09-03.
Other skills, from other repositories
hook-management
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
qa-testing
Generate and execute API and E2E tests with quality gate assessment.
test-automation
Plan, write, and review automated tests following KATA (Komponent Action Test Architecture) on Playwright + TypeScript, or explain existing automated tests in a sealed read-only mode. Use when writing E2E or API/integration tests, creating Page or Api components, designing ATCs, parameterizing test data, registering…
framework-development
Framework evolution mode — evolves the QA boilerplate itself (KATA, fixtures, cli/, scripts/, api/schemas/ pipeline, package.json deps). Self-contained Plan → Code → Verify → Archive pipeline; runs under the gentle-ai install --preset minimal install (no SDD- skills required). Use when adding new fixture APIs…
agentic-qa-core
Foundation skill that hosts shared references cited by other workflow skills (briefing template, dispatch patterns, orchestration doctrine, skill composition strategy). Loaded on demand by shift-left-testing, sprint-testing, test-documentation, test-automation, regression-testing, project-discovery, adapt-framework…