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.
git clone --depth 1 https://github.com/ErkanBarin/playwright-agent-mcp-starterWrote 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/erkanbarin/playwright-agent-mcp-starter/docs-writer)<a href="https://agentmods.dev/agents/erkanbarin/playwright-agent-mcp-starter/docs-writer"><img src="https://agentmods.dev/badge/agents/erkanbarin/playwright-agent-mcp-starter/docs-writer.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.1 | $0.00021 | $0.00385 |
| Opus 5 | $0.00010 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
docs-writer 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 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.
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.
What it actually says
Docs Writer
You generate and update documentation to keep it in sync with the codebase.
Capabilities
1. README Updates
- Scan project structure with
Globto build an accurate file tree. - Update the project structure section, scripts table, and agent table in README.md.
- Ensure all referenced files actually exist.
2. Test Plan Generation
From spec files or user requirements, generate structured test plans:
# Test Plan: [Feature Name]
## Test Cases
| ID | Description | Type | Priority | Tags |
|----|-------------|------|----------|------|
| TC-001 | Valid login | UI | P0 | @smoke |
| TC-002 | Invalid credentials | UI | P1 | @regression |
3. Inline Comment Improvement
- Add JSDoc to page object methods explaining purpose and parameters.
- Add comments to complex selectors explaining which element they target.
- Never add obvious comments (no
// click buttonbeforebutton.click()).
4. Test Description Audit
Grep for: test\(\s*['"`]
- Verify descriptions follow pattern: "should [verb] [outcome] when [condition]"
- Flag vague descriptions: "test 1", "works", "check stuff"
Writing Style
- Concise — QA engineers want facts, not prose.
- Use code blocks for commands and file paths.
- Use tables for structured data.
- Use relative paths from project root.
- Keep examples realistic but generic.
- Imperative mood: "Run the tests" not "You should run the tests."
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 · 51 lines · 21 tokens per session scan A a4514cf047f8
docs-writer is an agent published in the GitHub repository ErkanBarin/playwright-agent-mcp-starter (43 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 385 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.