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 exiao/pm-skills --skill verify-featuregit clone --depth 1 https://github.com/exiao/pm-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/exiao/pm-skills/verify-feature)<a href="https://agentmods.dev/skills/exiao/pm-skills/verify-feature"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/verify-feature/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/exiao/pm-skills/verify-feature"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/verify-feature.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.00163 | $0.05722 |
| Opus 5 | $0.00081 | $0.02861 |
| Sonnet 5 | $0.00033 | $0.01144 |
| Haiku 4.5 | $0.00016 | $0.00572 |
Grade A, and why
verify-feature 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.
| Server / API | socket | send the request, capture the response (curl/httpie) | How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Feature
Verification is runtime observation. You build the app, run it, drive it to where the changed code executes, and capture what you see. That capture is your evidence. Nothing else is.
This is the difference between "I ran the tests" and "I drove the actual changed code through its real interface and watched it behave." Only the second is verification.
What verification is NOT
- Not running tests. Running them proves you can run CI, not that the change works. Not as a warm-up, not "just to be sure," not as a regression sweep after. The time goes to running the app instead.
- Not typechecking. Same reason.
- Not import-and-call.
from src.foo import bar; print(bar(x))is a unit test you just wrote. Calling a function in isolation only proves the function works in isolation. Find the real caller that reaches a user-facing surface. - Not re-reading the code or re-running CI.
Step 1 — Find the change
The diff is ground truth. Any description of it is a claim. Read both; if they disagree, that's a finding.
git diff --stat origin/HEAD... # committed vs base
git diff HEAD --stat # uncommitted working tree
gh pr diff <n> # PR context
State the commit count. If the diff is large, redirect to a file and read it. If there's no repo diff, say so and use the scope the user named.
Step 2 — Identify the runtime surface
The surface is where a user or program interacts with the changed behavior. Map the change to its surface and drive it there:
| Change reaches | Surface | What you do |
|---|---|---|
| CLI / TUI | terminal | type the command, capture the pane (ShellExec; interactive-cli-driving for prompts) |
| Server / API | socket | send the request, capture the response (curl/httpie) |
| Web / UI (browser) | pixels | drive it and capture with shot-scraper — mandatory, see below |
| iOS-native GUI | pixels | drive it (ios-simulator), screenshot |
What ships with it
4 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.
- 8d ago First seen · 404 lines · 163 tokens per session scan A 7efdbc314a79
verify-feature is a skill published in the GitHub repository exiao/pm-skills (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 163 tokens to every session and 5,722 once invoked, about $0.0008 per session on Opus 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-08-31.
Other skills, from other repositories
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.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
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…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…