A post-merge user acceptance testing workflow for checking that a bug fix works in a test environment. It compares results before and after the change and records evidence in Jira.

Use it to follow Jira reproduction steps, compare the old and corrected behaviour, attach evidence, and move the ticket when the check passes.

It provides a repeatable way to confirm a fix and avoid marking a bug complete without proof.

verify-bug — Skill for Codex by HoangNguyen0403

Install

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.

Any agent

npx skills add HoangNguyen0403/agent-skills-standard --skill verify-bug

Clone the repo

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/verify-bug/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/verify-bug)

Your own site

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/verify-bug"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/verify-bug/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/verify-bug"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/verify-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,286 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.01286
Opus 5	$0.00019	$0.00643
Sonnet 5	$0.00008	$0.00257
Haiku 4.5	$0.00004	$0.00129

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

Security

Grade A, and why

verify-bug 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 9d 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.

.codex/skills/verify-bug/SKILL.md · 128 lines

How it starts

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

Verify Bug Skill

[!IMPORTANT] Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Instructions

When the user asks to perform this workflow, execute the following steps:

Verify-Bug — UAT Audit

Goal: Prove a bug fix works in the UAT environment via comparative Before/After evidence, then transition ticket status.

Input

/verify-bug <jira-url-or-key> [--baseline-image <url>]

Workflow

Step 0: Pre-flight & Data Gathering

[!TIP] Sub-Agent Delegation: If your platform supports sub-agents (e.g., Claude, OpenCode, Gemini, Kiro), delegate steps 1-3 below to your JIRA Analyst sub-agent (e.g., @specialist-jira-analyst). If sub-agents are NOT supported (e.g., Antigravity, Windsurf), you must execute these steps yourself.

Parse JIRA: Extract Market, Reproduce steps, and Expected Result.
Resolve Markets: If multiple markets, prompt for scope (Full/Sample/Custom).
Fetch Test Data: Call Confluence for Test data - <MARKET> UAT. Parse credentials and module-specific data (e.g., customer codes).
Credential Check: Rule out expired accounts before starting sessions.
Fallback: If Jira/Confluence MCPs are unavailable, request exported ticket/test-data text and continue with local evidence.

Step 1: Comparative Audit (Execution Phase)

For each market in scope:

Environment Setup: Run the DNS probe from <SKILLS>/common/common-web-visual-testing/references/diagnostic-decoder.md; if it indicates VPN is required, connect VPN and retry.
Named Session: Start playwright-cli -s={TICKET}-{MARKET} or Appium session.
Walk Steps: Execute reproduction steps.
- Hover Discipline: Always hover the target element (warning, button, price) before screenshotting.
- Stability: Disable animations and mask dynamic fields (clocks, balances).
Verdict Determination:
- PASS: End-state matches Expected Result.
- FAIL: End-state matches Actual Result or original bug screenshot.
- NEEDS-HUMAN: Deviates from both.

Read the full file on GitHub · 128 lines

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.

9d ago First seen · 128 lines · 39 tokens per session scan A aff3a2e19afc

Subscribe to this mod's changes

verify-bug is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 1,286 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.

Debugging E2E testing React Testing best-practices coding-standards flutter nestjs nextjs

verify

Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).

meursyphus/ssgoi · 26 tokens

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…

PostHog/posthog · 112 tokens

verify-bug