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 jpoehnelt/skills --skill agents-create-verification-skillgit clone --depth 1 https://github.com/jpoehnelt/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/jpoehnelt/skills/agents-create-verification-skill)<a href="https://agentmods.dev/skills/jpoehnelt/skills/agents-create-verification-skill"><img src="https://agentmods.dev/badge/skills/jpoehnelt/skills/agents-create-verification-skill/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/jpoehnelt/skills/agents-create-verification-skill"><img src="https://agentmods.dev/badge/skills/jpoehnelt/skills/agents-create-verification-skill.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.00070 | $0.00897 |
| Opus 5.5 | $0.00028 | $0.00359 |
| Sonnet 5.5 | $0.00014 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
agents-create-verification-skill scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Drive.** Prefer an existing harness: `ls` for `playwright.config.*`, `cypress.config.*`, e2e folders, health or metrics endpoints, or curl-able routes. Otherwise use Playwright for web, a tmux or PTY session for CLI How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a verification skill
Produce .agents/skills/verify-<surface>/SKILL.md, a skill that launches the real app, exercises a feature the way a user would, and captures evidence. The next agent reads it cold, so it must work from the file alone. Every command in it must be real.
Repo facts (from AGENTS.md, CLAUDE.md, or README.md): the local run command, ports, seed users and data, auth, the existing e2e harness, and any skill that already covers rendered UI evidence.
1. Interview the repo, not the user
Answer from the codebase. Ask the user in chat only about what you cannot observe.
- Surface. Web UI, CLI, TUI, API, desktop, mobile, or device. Pick the primary one; a repo with several gets one skill per surface.
- Run. Read
package.jsonscripts,Makefile,README.md, andAGENTS.mdfor the documented start command, ports, env vars, seed data, and auth. Prefer a one-command local stack when the repo has one. - Drive. Prefer an existing harness:
lsforplaywright.config.*,cypress.config.*, e2e folders, health or metrics endpoints, or curl-able routes. Otherwise use Playwright for web, a tmux or PTY session for CLI and TUI, and plain HTTP (curl) for services. If an existing skill already covers this surface, extend it instead. - Observe. Screenshots, response bodies, logs, exit codes, database state.
- Isolate. Can two instances run side by side? If not, the skill must say so.
If the checkout does not build or start, report that precisely before generating anything.
2. Write the skill
Frontmatter: name: verify-<surface>, and a description naming the app, the surface, and "Use when ...". Sections:
- Launch. The exact start command and how to tell it is ready (a log line or a health response). It must work from an empty data directory, including migrations and seed data. Include teardown.
- Doctor. One read-only check: process up, right build, port owned by this run, auth valid.
- Drive. Real selectors and commands from this repo. Prefer ARIA roles, labels, and data attributes over coordinates.
- Evidence. What to capture and where. Exercise the real user path, not test-only endpoints. Capture the action and the resulting state. Verify side effects such as files, rows, and messages. Mock only at an existing production boundary.
- Cleanup. Stop only what the run started, never by process name. Keep the evidence, including failure evidence.
- Helpers. Any shipped script is
bashwithset -euo pipefail, executable, and shown in the skill body. Keep fragile prerequisites in the script, not copied into prose.
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.
- 8d ago Changed · -1 lines de60bbadc37a
- 9d ago First seen · 52 lines · 70 tokens per session scan A ae5a4803685e
agents-create-verification-skill is a skill published in the GitHub repository jpoehnelt/skills (23 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 897 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-21.
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).
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.
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".
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.
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…