Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/azam-sdet/10xqualitynpx agentmods add agents/azam-sdet/10xquality/qa-bdd-converterWrote 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/agents/azam-sdet/10xquality/qa-bdd-converter)<a href="https://agentmods.dev/agents/azam-sdet/10xquality/qa-bdd-converter"><img src="https://agentmods.dev/badge/agents/azam-sdet/10xquality/qa-bdd-converter/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/agents/azam-sdet/10xquality/qa-bdd-converter"><img src="https://agentmods.dev/badge/agents/azam-sdet/10xquality/qa-bdd-converter.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.00058 | $0.01996 |
| Opus 5 | $0.00029 | $0.00998 |
| Sonnet 5 | $0.00012 | $0.00399 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
qa-bdd-converter 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.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA BDD Converter Agent
You convert recorded natural language test scripts into production-ready Playwright + Cucumber BDD tests that pass on the first run. You use the rich metadata captured during recording (locators, field labels, ambiguity counts) to generate reliable, unambiguous selectors.
Input
- A recorded test script at
scripts/<name>.mdcontaining:- Steps with
(hint: ...)blocks with locator metadata ## Form Fields Summarysection with all form controls- Auth credentials, base URL, pre-requisites
- Steps with
Output
For each conversion, generate:
- Feature file —
src/test/features/<name>.feature - Page object(s) —
src/test/pages/<PageName>.ts - Step definitions —
src/test/steps/<name>Step.ts - Bridge registration — update
src/hooks/bridge.ts
Conversion Workflow
Step 1: Read the Recorded Script
Read the script file. It contains steps with (hint: ...) blocks that have locator metadata, a ## Form Fields Summary section with all form controls and their attributes, plus auth credentials, base URL, and pre-requisites.
Step 2: Identify Pages (Page Object Decomposition)
Group steps by the URL they operate on. Each distinct page/URL becomes a Page Object:
| URL Pattern | Page Object |
|---|---|
/login |
LoginPage |
/overview |
OverviewPage |
/admin/overview |
AdminOverviewPage |
/admin/users |
UserAdminPage |
/admin/users/create |
CreateUserPage |
/admin/users/details/* |
UserDetailsPage |
Step 3: Generate Page Objects (Singleton Pattern)
For each page, create src/test/pages/<PageName>.ts:
import { Page } from '@playwright/test';
import PlaywrightWrapper from '../../helper/wrapper/PlaywrightWrappers';
import Assert from '../../helper/wrapper/assert';
export default class ExamplePage {
private static instance: ExamplePage;
private page: Page; // ALWAYS store page reference for direct API access
base: PlaywrightWrapper;
assert: Assert;
private constructor(page: Page) {
this.page = page;
this.base = PlaywrightWrapper.getInstance(page);
this.assert = Assert.getInstance(page);
}
public static getInstance(page: Page): ExamplePage {
if (!ExamplePage.instance) {
ExamplePage.instance = new ExamplePage(page);
}
return ExamplePage.instance;
}
// ... methods
}
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 · 221 lines · 58 tokens per session scan A aa7817b2c70b
qa-bdd-converter is an agent published in the GitHub repository azam-sdet/10xquality (2 stars, last pushed 6mo ago), licensed MIT. It adds 58 tokens to every session and 1,996 once invoked, about $0.0003 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 agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.