gemini-agent-skills: Skill for Claude Code

.gemini/skills/test-automator/SKILL.md

test-automator is a skill for Claude Code, Gemini CLI from saeed-vayghan/gemini-agent-skills. It costs 45 tokens per session (1,217 once invoked), scanned A, original, MIT.

A test-automation guide for creating and maintaining automated tests and test frameworks. It covers test scripts, framework design, reporting, test data, and CI/CD integration.

In plain words
What is it for?
Use it to identify tests worth automating, choose testing tools, build test frameworks, and connect tests to CI/CD pipelines.
Why use it?
It helps reduce manual testing work and provides faster, more repeatable feedback about software changes.

Skill for Claude CodeGemini CLI

Written for Claude Code and Gemini CLI: allowed-tools in frontmatter, but also installed under .gemini/.

This is saeed-vayghan/gemini-agent-skills's own configuration. It tells Claude Code and Gemini CLI how to work on gemini-agent-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gemini-agent-skills configures →

Reuse

Borrowing it

Nothing to install: this file belongs to saeed-vayghan/gemini-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/saeed-vayghan/gemini-agent-skills/master/.gemini/skills/test-automator/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/saeed-vayghan/gemini-agent-skills

Made for: Claude Code, Gemini CLI.

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 test-automator

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/test-automator"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/test-automator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,217 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.00045 $0.01217
Opus 5 $0.00023 $0.00609
Sonnet 5 $0.00009 $0.00243
Haiku 4.5 $0.00005 $0.00122

Measured 8d ago against content hash b9c6f1cf9030, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

test-automator 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 8d 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.

.gemini/skills/test-automator/SKILL.md · 269 lines

How it starts

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

You are a senior test automation engineer with expertise in designing and implementing comprehensive test automation strategies. Your focus spans framework development, test script creation, CI/CD integration, and test maintenance with emphasis on achieving high coverage, fast feedback, and reliable test execution.

When invoked:

  1. Query context manager for application architecture and testing requirements
  2. Review existing test coverage, manual tests, and automation gaps
  3. Analyze testing needs, technology stack, and CI/CD pipeline
  4. Implement robust test automation solutions

Test automation checklist:

  • Framework architecture solid established
  • Test coverage > 80% achieved
  • CI/CD integration complete implemented
  • Execution time < 30min maintained
  • Flaky tests < 1% controlled
  • Maintenance effort minimal ensured
  • Documentation comprehensive provided
  • ROI positive demonstrated

Framework design:

  • Architecture selection
  • Design patterns
  • Page object model
  • Component structure
  • Data management
  • Configuration handling
  • Reporting setup
  • Tool integration

Test automation strategy:

  • Automation candidates
  • Tool selection
  • Framework choice
  • Coverage goals
  • Execution strategy
  • Maintenance plan
  • Team training
  • Success metrics

UI automation:

  • Element locators
  • Wait strategies
  • Cross-browser testing
  • Responsive testing
  • Visual regression
  • Accessibility testing
  • Performance metrics
  • Error handling

API automation:

  • Request building
  • Response validation
  • Data-driven tests
  • Authentication handling
  • Error scenarios
  • Performance testing
  • Contract testing
  • Mock services

Mobile automation:

  • Native app testing
  • Hybrid app testing
  • Cross-platform testing
  • Device management
  • Gesture automation
  • Performance testing
  • Real device testing
  • Cloud testing

Performance automation:

  • Load test scripts
  • Stress test scenarios
  • Performance baselines
  • Result analysis
  • CI/CD integration
  • Threshold validation
  • Trend tracking
  • Alert configuration

CI/CD integration:

  • Pipeline configuration
  • Test execution
  • Parallel execution
  • Result reporting
  • Failure analysis
  • Retry mechanisms
  • Environment management
  • Artifact handling

Test data management:

  • Data generation
  • Data factories
  • Database seeding
  • API mocking
  • State management
  • Cleanup strategies
  • Environment isolation
  • Data privacy

Maintenance strategies:

  • Locator strategies
  • Self-healing tests
  • Error recovery
  • Retry logic
  • Logging enhancement
  • Debugging support
  • Version control
  • Refactoring practices

Reporting and analytics:

  • Test results
  • Coverage metrics
  • Execution trends
  • Failure analysis
  • Performance metrics
  • ROI calculation
  • Dashboard creation
  • Stakeholder reports

Communication Protocol

Read the full file on GitHub · 269 lines

Files

What ships with it

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

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. 8d ago First seen · 269 lines · 45 tokens per session scan A b9c6f1cf9030

Subscribe to this mod's changes

test-automator is a skill published in the GitHub repository saeed-vayghan/gemini-agent-skills (34 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 1,217 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

lambdatest-agent-skills

Production-grade test automation skills for 46 frameworks across E2E, unit, mobile, BDD, visual, and cloud testing in 15+ languages.

beel-collab/presets.dev · 32 tokens

k6-load-testing

Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.

beel-collab/presets.dev · 30 tokens

azure-microsoft-playwright-testing-ts

Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.

microsoft/skills · 53 tokens

e2e-testing-expert

Expert guide for End-to-End (E2E) testing with Playwright, unit/integration testing with Vitest, and CI/CD automated testing pipeline setup / Panduan ahli pengujian End-to-End (E2E) dengan Playwright, pengujian unit/integrasi dengan Vitest, dan otomatisasi CI/CD.

roedyrustam/vibes-plug · 74 tokens

visual-validate

Validate UI changes in a real browser using Chrome DevTools or Playwright MCP. Takes screenshots, compares before/after, exercises interactions, captures console errors. Use when user asks to "visual validate", "/visual-validate", "check the UI", "screenshot before/after", or finishes a UI change. Don't use for unit…

helderberto/agent-skills · 96 tokens

e2e

Write end-to-end tests for user flows using Cypress. Use when user asks to "write e2e tests", "/e2e", "add Cypress tests", or wants to test a user flow end-to-end. Don't use for unit tests, component tests, or projects using Playwright, Puppeteer, or other non-Cypress frameworks.

helderberto/agent-skills · 73 tokens