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 instructions/tahanima/playwright-java-test-automation-architecture/gemini-mdgit clone --depth 1 https://github.com/Tahanima/playwright-java-test-automation-architectureWrote 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/instructions/tahanima/playwright-java-test-automation-architecture/gemini-md)<a href="https://agentmods.dev/instructions/tahanima/playwright-java-test-automation-architecture/gemini-md"><img src="https://agentmods.dev/badge/instructions/tahanima/playwright-java-test-automation-architecture/gemini-md.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.00939 | $0.00939 |
| Opus 5 | $0.00469 | $0.00469 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
playwright-java-test-automation-architecture GEMINI.md 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 5d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project: Playwright Java Test Automation Architecture
Context & Tech Stack
- Build Tool: Gradle (using
build.gradle) - Language: Java 17+
- Browser Automation Library: Playwright
- Architecture: Data-driven test automation using POM to model and reuse web page functionality.
- Base Package:
io.github.tahanima - Test Runner: JUnit 5 with custom annotations (
@TestDataSource,@Validation,@Smoke,@Regression).
Project Mapping
- Pages:
src/main/java/io/github/tahanima/ui/page/– Encapsulate low-level page actions and locators. - Components:
src/main/java/io/github/tahanima/ui/component/– Reusable UI elements (Header, SideNav, etc.). - TestData POJOs:
src/main/java/io/github/tahanima/testdata/– Business logic layer that interprets CSV data and interacts with Pages. - Tests:
src/test/java/io/github/tahanima/e2e/– High-level orchestration; must extendBaseTest. - Test Data Files:
src/test/resources/testdata/– CSV files for data-driven inputs. - Utilities:
BrowserManager.java– Browser lifecycle management.CsvLoader.java– CSV loading for test data.
- Factories:
BasePageFactory.java– Centralized page initialization.BrowserFactory.java– Abstracts browser setup and creation.
- Reporting:
AllureManager.java– Custom logging, screenshots, and test reporting.
Development Rules
- Instantiation: Do not use
new LoginPage(). Always use theBasePageFactoryto initialize pages. - Logic Placement:
- Pages/Components: Handle locators and atomic actions (e.g.,
typeUsername). - TestData POJOs: Handle business workflows (e.g.,
loginWith(LoginTestData data)). - Tests: Handle assertions and test flow. Minimal direct Playwright API calls here.
- Pages/Components: Handle locators and atomic actions (e.g.,
- Stability & Waits:
- No Hard Sleeps: Never use
Thread.sleep(). Rely on Playwright’s auto-waiting orpage.waitForCondition(). - Web-First Assertions: Use
PlaywrightAssertions.assertThat()for UI states to enable automatic retries.
- No Hard Sleeps: Never use
- Configuration: Use
ConfigurationManagerto accessconfig.properties. Do not hardcode URLs or credentials. - Data Loading: Use the custom
@TestDataSourceannotation for CSV data-driven tests. - Naming Conventions:
- Pages →
*Page.java - Components →
*Component.java - Test Data POJOs →
*TestData.java(must extendBaseTestData).
- Pages →
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.
- 5d ago First seen · 78 lines · 939 tokens per session scan A f26ba9636b09
playwright-java-test-automation-architecture GEMINI.md is an instructions file published in the GitHub repository Tahanima/playwright-java-test-automation-architecture (112 stars, last pushed 6mo ago), licensed MIT. It adds 939 tokens to every session, about $0.0047 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-30.
Other instructions, from other repositories
keploy AGENTS.md
AGENTS.md instructions for keploy/keploy, covering agents.md, what this project is, build, run, lint, test, build the binary and standard build (what ci calls "build-no-race").
e2e-testing CLAUDE.md
Claude Code instructions for burhankhatri/e2e-testing, covering claude.md — development methodology, critical rules, workflow decision tree, skill priority and the inverted testing pyramid.
playwright CLAUDE.md
Claude Code instructions for microsoft/playwright, covering monorepo packages, browser packages, tooling packages, key directories and build.
playwright copilot-instructions.md
Copilot instructions for microsoft/playwright, a project described as: Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
playwright-mcp CLAUDE.md
Claude Code instructions for microsoft/playwright-mcp, covering commit convention, ... make changes .., summary, rolling playwright and preparing a release.
playwright-rust CLAUDE.md
Instructions for padamson/playwright-rust, covering claude.md, project, repository layout, skills (procedural reference) and documentation hierarchy.