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 cuongtl1992/vibe-skills --skill pom-generatorgit clone --depth 1 https://github.com/cuongtl1992/vibe-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/cuongtl1992/vibe-skills/pom-generator)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/pom-generator"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/pom-generator/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/cuongtl1992/vibe-skills/pom-generator"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/pom-generator.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.00035 | $0.01357 |
| Opus 5 | $0.00017 | $0.00678 |
| Sonnet 5 | $0.00007 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
pom-generator 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 12d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
POM Generator Skill
Automatically generate Page Object Model classes by analyzing live web pages using Playwright MCP.
When to Use
- Creating a new Page Object for a web page
- Analyzing page elements to identify selectors
- Generating POM code following best practices
- Setting up POM structure for a new project
Workflow
Step 1: Navigate to Page
Use Playwright MCP to navigate to the target URL:
mcp__playwright__playwright_navigate(url: "https://example.com/login")
Step 2: Capture Page State
Take a screenshot and get HTML for analysis:
mcp__playwright__playwright_screenshot(name: "page_analysis", fullPage: true)
mcp__playwright__playwright_get_visible_html(cleanHtml: true, removeStyles: true)
Step 3: Analyze Elements
Identify interactive elements from HTML:
| Element Type | Look For |
|---|---|
| Inputs | <input>, <textarea>, <select> |
| Buttons | <button>, input[type="submit"], clickable <span>, <a> |
| Forms | <form> with action/method |
| Navigation | <a href>, routing links |
| Feedback | Error divs, alerts, toasts, modals |
Step 4: Generate Code
- Check for BasePage - If project doesn't have BasePage, create it first (see base-page-template.md)
- Generate Page Object - Create class extending BasePage with:
- Selectors object (private readonly)
- Navigation method
- Form filling methods
- Action methods
- Validation methods
Step 5: Close Browser
mcp__playwright__playwright_close()
Code Generation Rules
Naming Conventions
| Item | Convention | Example |
|---|---|---|
| File | snake_case.ts |
login_page.ts |
| Class | PascalCase |
LoginPage |
| Methods | camelCase |
fillUsername() |
| Selectors | camelCase |
usernameInput |
Selector Priority
Choose selectors in this order (see selector-strategies.md):
What ships with it
3 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.
- 12d ago First seen · 223 lines · 35 tokens per session scan A 411256252359
pom-generator is a skill published in the GitHub repository cuongtl1992/vibe-skills (10 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,357 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…