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 skills/bryan-gu/e2e_testskill/e2e_testskillnpx skills add bryan-gu/E2E_TestSKILL --skill e2e_testskillgit clone --depth 1 https://github.com/bryan-gu/E2E_TestSKILLWhat 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.00074 | $0.00326 |
| Opus 5 | $0.00037 | $0.00163 |
| Sonnet 5 | $0.00015 | $0.00065 |
| Haiku 4.5 | $0.00007 | $0.00033 |
Grade A, and why
bf-test-workflow 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 25 lines · 74 tokens per session scan A 1b07dc795669
bf-test-workflow is a skill published in the GitHub repository bryan-gu/E2E_TestSKILL (10 stars, last pushed 2mo ago), with no licence file. It adds 74 tokens to every session and 326 once invoked, about $0.0004 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
CBrowser
Cognitive Browser — AI browser automation that simulates real user cognition. 122 MCP tools, 21 personas, 25 cognitive traits, constitutional safety, cognitive journeys with LLM-free trace replay, screen capture to GIF/WebP/WebM with an AI-readable frame manifest (v18.69.3). USE WHEN browser automation OR cognitive…
flow-tester
Tests a web application by discovering its user flows, driving a real Chromium browser through them while streaming a live dashboard, and judging each screen with vision. Flags functional failures, incorrect content, visual/layout problems, and console/network errors. On a local codebase it also runs a read-only…
triage-e2e
Run all E2E tests, categorize failures (known issue, app bug, test update, flaky, new), cross-reference Jira, and generate a management-ready report.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-test-results
Query Playwright CI test results from the aggregated DuckDB database. Answers questions about flaky tests, failure rates, slow tests, and per-run/SHA/PR results without hunting through GitHub artifacts.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.