create-handover-test

create-handover-test is a skill for Claude Code from agentmantis/test-skills. It costs 70 tokens per session (1,176 once invoked), scanned A, original, MIT.

A workflow for creating a ticket-specific Playwright end-to-end test, meaning a test that checks a feature through the application as a user would. It places the test in a handover suite and follows a later promotion process.

In plain words
What is it for?
Use it to write a handover, ticket, or functional test for a specific change, including any needed page-object methods and test data.
Why use it?
It provides a consistent way to turn acceptance criteria from a ticket into a runnable test. It also keeps ticket references, test data, and page interactions aligned with the existing test structure.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { test } from '../../fixtures/base';.

Good fit Use it to write a handover, ticket, or functional test for a specific change, including any needed page-object methods and test data.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/agentmantis/test-skills
agentmods
npx agentmods add skills/agentmantis/test-skills/create-handover-test

Made for: Claude Code.

Wrote 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.

agentmods badge for create-handover-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentmantis/test-skills/create-handover-test/github.svg)](https://agentmods.dev/skills/agentmantis/test-skills/create-handover-test)
Your own site
<a href="https://agentmods.dev/skills/agentmantis/test-skills/create-handover-test"><img src="https://agentmods.dev/badge/skills/agentmantis/test-skills/create-handover-test/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.

agentmods 80×15 button for create-handover-test

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentmantis/test-skills/create-handover-test"><img src="https://agentmods.dev/badge/skills/agentmantis/test-skills/create-handover-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,176 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.01176
Opus 5.5 $0.00028 $0.00470
Sonnet 5.5 $0.00014 $0.00235
Haiku 4.5 $0.00007 $0.00118

Measured 1mo ago against content hash b995b2d5d0a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-handover-test 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.

skills/create-handover-test/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Handover Test

Generate a ticket-driven handover test that validates specific acceptance criteria.


Workflow

  1. Parse the ticket key and description from the user's request (e.g., PROJ-456 bulk export)
  2. Check if a POM exists for the page under test in e2e/poms/
    • If yes, read it and add any new methods needed for this ticket's acceptance criteria
    • If no, create one first using the create-pom skill
  3. Check if test data exists — create or update as needed
  4. Create the spec file in e2e/tests/handover/
  5. Run the test to verify it passes:
    npx playwright test --project="chromium:handover" {TICKET}-{description}.spec.ts
    

Naming Convention

Filename

{TICKET}-{short-description}.spec.ts
  • {TICKET} — The ticket key exactly as it appears in the tracker (e.g., PROJ-456, MANT-123)
  • {short-description} — Brief kebab-case summary (NOT the full ticket title)

Examples:

  • PROJ-456-bulk-export.spec.ts
  • MANT-123-vault-bulk-delete.spec.ts
  • FEAT-789-user-avatar-upload.spec.ts

test.describe Block

The outer test.describe must include the ticket key for traceability:

test.describe('PROJ-456: Bulk Export', () => {

Spec Structure

import { test } from '../../fixtures/base';
import { getAuthFilePath } from '../../helpers/env-config';
import { FeaturePage } from '../../poms/feature.page';

const authFile = getAuthFilePath();

test.describe('PROJ-456: Bulk Export', () => {
    test.beforeAll(async ({ browser }) => {
        const context = await browser.newContext({
            storageState: authFile,
        });
        const page = await context.newPage();
        const pom = new FeaturePage(page);
        await pom.setUp();
        await page.close();
        await context.close();
    });

    test('should export selected items as CSV', async ({ page, testData }) => {
        const pom = new FeaturePage(page);
        const items = testData.feature.items;

        await pom.navigateToPage();
        // ... validate acceptance criteria from ticket
    });

    test('should show error when no items selected', async ({ page }) => {
        const pom = new FeaturePage(page);

        await pom.navigateToPage();
        // ... validate error handling criteria
    });
});

Read the full file on GitHub · 149 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 149 lines · 70 tokens per session scan A b995b2d5d0a7

Subscribe to this mod's changes

create-handover-test is a skill published in the GitHub repository agentmantis/test-skills (12 stars, last pushed 6mo ago), licensed MIT. It adds 70 tokens to every session and 1,176 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

critique

Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens