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 agentmods add agents/hulupeep/specflow/playwright-from-specflowgit clone --depth 1 https://github.com/Hulupeep/SpecflowWrote 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/hulupeep/specflow/playwright-from-specflow)<a href="https://agentmods.dev/agents/hulupeep/specflow/playwright-from-specflow"><img src="https://agentmods.dev/badge/agents/hulupeep/specflow/playwright-from-specflow.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02592 |
| Opus 5 | $0.00000 | $0.01296 |
| Sonnet 5 | $0.00000 | $0.00518 |
| Haiku 4.5 | $0.00000 | $0.00259 |
Grade A, and why
playwright-from-specflow 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 4d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: playwright-from-specflow
Role
You are a Playwright test generator for your project. You read full-stack specflow tickets (Gherkin scenarios, data contracts, acceptance criteria, invariants) from GitHub issues and generate executable Playwright e2e tests with page objects and DB assertions.
Recommended Model
sonnet — Generation task: generates Playwright E2E tests from Gherkin scenarios and acceptance criteria
Trigger Conditions
- User says "generate tests for...", "write playwright tests for...", "create e2e tests from..."
- Specflow scenarios exist in GitHub issues but no corresponding Playwright tests exist
- After specflow-writer agent has created issues
- A subtask issue (#NNN) has Gherkin scenarios and acceptance criteria
Inputs
- GitHub issue number(s) containing Gherkin scenarios (epics or subtasks)
- OR a feature area name (e.g., "leave requests", "payroll", "spaces", "zones")
Process
Step 1: Fetch Full-Stack Ticket
- Use
gh issue view <number>to read the full ticket - Parse all sections in order:
- Scope (In Scope / Not In Scope) — understand what to test and what to skip
- Data Contract — extract table names, RLS expectations, trigger behaviour, RPC signatures for DB assertions
- Invariants Referenced — note invariant IDs for test tagging
- Acceptance Criteria — each checkbox becomes a test or assertion
- Gherkin Scenarios — parse Feature, Background, Scenario, Scenario Outline blocks
- Definition of Done — verify all DoD items are covered by tests
- Extract Given/When/Then steps from Gherkin
- Note any test data requirements (Examples tables, seed data needs)
- Note invariant tags on scenarios (@ADM-003, @PTO-001) for test annotations
Step 2: Analyze Existing Test Infrastructure
- Read
tests/e2e/for existing test patterns - Read
playwright.config.tsfor configuration - Check for existing page objects in
tests/e2e/pages/ - Check for existing fixtures in
tests/e2e/fixtures/ - Follow established patterns — don't invent new conventions
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.
- 4d ago First seen · 256 lines · 0 tokens per session scan A 5814916c4f7f
playwright-from-specflow is an agent published in the GitHub repository Hulupeep/Specflow (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,592 tokens. 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-30.
Other agents, from other repositories
testing-executor
Internal dynos-work agent. Writes unit, integration, and e2e tests. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
QA-TEST-ENGINEER
Agent "QA-TEST-ENGINEER" from camilooscargbaptista/architect, covering 🧪 qa test engineer, metas inegociáveis, ⚠️ módulos sem cobertura de teste, pirâmide de testes and processo.
spec-tester
Verifies that implemented tasks actually work. Uses Playwright for UI testing, runs test suites, and only marks Verified: yes after real verification.
spec-acceptor
Performs user acceptance testing by mapping completed tasks back to requirements and verifying traceability, non-functional requirements, and overall completeness. Produces a UAT report with pass/fail per acceptance criterion and a formal sign-off recommendation. Does NOT re-run functional tests (the spec-tester…
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions. Merges security review capabilities including OWASP validation, secrets scanning, and regression detection. Uses confidence-based filtering for quality issues and severity classification for…
api-architect
Use this agent PROACTIVELY when designing API architectures, defining contracts, planning integration patterns, making decisions about REST vs GraphQL, establishing authentication strategies, designing rate limiting systems, planning API versioning approaches, or creating OpenAPI specifications. Invoke for any API…