Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/testing/write-manual-browser-test/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/skills/hlalljie/agent-workflow-presets/write-manual-browser-test)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/write-manual-browser-test"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/write-manual-browser-test/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/skills/hlalljie/agent-workflow-presets/write-manual-browser-test"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/write-manual-browser-test.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.00041 | $0.00296 |
| Opus 5 | $0.00020 | $0.00148 |
| Sonnet 5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
write-manual-browser-test 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.
What it actually says
Write manual browser test
Job
Create or revise tests/manual/<area>-<slug>.md so an agent or human can run the same flow later via run manual browser test.
Automated tests live in tests/*.test.ts. This skill is only the browser checklist doc.
Steps
- Copy TEMPLATE.md if new file.
- Start state — exact server command + env, URL, agent notes. Incomplete = invalid.
- Procedure — numbered steps; pass / fail observable.
- Optional Vitest prerequisite — shell to run before browser (not part of browser steps).
- Add a bullet under
tests/manual/README.mdif new area.
Naming
tests/manual/<area>-<short-slug>.md
Called from
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 31 lines · 41 tokens per session scan A 0110ad3198ca
write-manual-browser-test is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 296 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-08-31.
Other skills, from other repositories
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
e2e-check
Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.
ac-qa-test-e2e
Executes E2E tests from definition files with Playwright browser automation. Triggers on keywords: test e2e, run e2e, execute e2e test, e2e test runner.
ac-qa-e2e-review
Reviews spec implementation with E2E visual browser validation via Playwright. Triggers on keywords: e2e review, visual review, spec review, browser validation.
ac-qa-browser
Opens browser at URL for E2E testing via playwright-cli. Provides CLI commands for navigation, screenshots, and interaction. Triggers on keywords: browser, open browser, playwright browser, e2e browser.
browser-playwright-check
Use when an agent needs to operate or verify a web page with Playwright, including screenshots, viewport checks, navigation, forms, clicks, canvas visibility, responsive layout, or local Panel/browser behavior.