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 agentmods add skills/gowtham012/claude-plugins/generate-testsnpx skills add gowtham012/Claude-plugins --skill generate-testsgit clone --depth 1 https://github.com/gowtham012/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/skills/gowtham012/claude-plugins/generate-tests)<a href="https://agentmods.dev/skills/gowtham012/claude-plugins/generate-tests"><img src="https://agentmods.dev/badge/skills/gowtham012/claude-plugins/generate-tests.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00318 |
| Opus 5 | $0.00019 | $0.00159 |
| Sonnet 5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
generate-tests 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 4d 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.
What it actually says
Generate tests from video: $ARGUMENTS
Arguments:
$0= video_path (required)$1= framework:playwrightorcypress(default:playwright)
Steps
- Call MCP tool
mcp__video-insight__generate_testswithvideo_path=$0,framework=$1(defaultplaywright). - Read keyframe images for each step to identify selectors.
- Map
inferred_actionto test commands:navigate→page.goto()/cy.visit()click_or_submit→page.locator('text=...').click()/cy.click()scroll→page.evaluate(scrollBy)/cy.scrollTo()observe→expect().toBeVisible()/cy.should('be.visible')
- Use
text_appearedfor visibility assertions,text_disappearedfor hidden assertions. - Wrap in
describe/testblocks. Output a single complete test file.
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.
- 4d ago First seen · 26 lines · 38 tokens per session scan A d719ec3b7e07
generate-tests is a skill published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 318 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-08-31.
Other skills, from other repositories
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.
vibe-e2e
Use when performing end-to-end verification before delivery. Launches the project, opens browser, verifies every page renders, every button works, every API responds. Triggers on "E2E", "end-to-end test", "真机验证", "交付验证", "跑一下看看", "打开浏览器验证".
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.
webapp-testing
Professional web application testing and automation using Playwright with support for multiple browsers, mobile emulation, screenshot capture, network interception, and comprehensive test assertions. Use for: (1) E2E testing across browsers, (2) UI automation, (3) Form testing and validation, (4) Visual regression…
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.