Borrowing it
Nothing to install: this file belongs to ballerina-platform/ballerina-vscode. 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/ballerina-platform/ballerina-vscode/main/.claude/skills/ballerina-e2e-writer/SKILL.mdgit clone --depth 1 https://github.com/ballerina-platform/ballerina-vscodeWrote 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/ballerina-platform/ballerina-vscode/ballerina-e2e-writer)<a href="https://agentmods.dev/skills/ballerina-platform/ballerina-vscode/ballerina-e2e-writer"><img src="https://agentmods.dev/badge/skills/ballerina-platform/ballerina-vscode/ballerina-e2e-writer/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/ballerina-platform/ballerina-vscode/ballerina-e2e-writer"><img src="https://agentmods.dev/badge/skills/ballerina-platform/ballerina-vscode/ballerina-e2e-writer.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.00038 | $0.01682 |
| Opus 5.5 | $0.00015 | $0.00673 |
| Sonnet 5.5 | $0.00008 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
ballerina-e2e-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 3d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ballerina E2E Writer
Use this skill when adding new Ballerina extension user-flow E2E coverage in
packages/ballerina-extension.
Scope: work only inside
packages/ballerina-extension. Do not edit thesubmodules/tree or shared/common libraries.
For user-facing instructions and prompt examples, see USER_GUIDE.md in this
skill directory.
Workflow
-
Read the requested scenario and existing tests in
packages/ballerina-extension/e2e-test/e2e-playwright-tests. Before writing anything, check whether an existing spec already covers the scenario — the tracking sheet can be out of date. If covered, document the real flow and flag gaps instead of duplicating. -
Ensure the Ballerina VSIX exists locally. The e2e harness installs from
packages/ballerina-extension/vsix/*.vsix. If none is found, build it:rush build -t ballerina -
Create
scenario.mdunder the authoring scenario directory before writing any step files:packages/ballerina-extension/e2e-test/e2e-authoring/scenarios/<scenario-name>/scenario.mdIf the user only described the scenario in the prompt, derive the steps and write
scenario.mdnow. If the user provided ascenario.mdpath, read it first. Keep it short: a prose paragraph describing one concrete, verifiable end-to-end flow, optionally with a steps table and a "Gaps" section. -
Write small step files in
steps/*.step.js. Keep each step focused and rerunnable. For diagram flows, steps must build the flow through the product UI: click the diagram plus button, open the node palette, search or select the node, fill the form, then save. -
Run the steps through the named daemon:
bash packages/ballerina-extension/e2e-test/e2e-authoring/scripts/run-steps.sh <scenario-name> packages/ballerina-extension/e2e-test/e2e-authoring/scenarios/<scenario-name>/steps -
If a selector is unstable or an element cannot be found by
data-testid, add a stabledata-testidattribute to that element in the relevantpackages/*/srcUI package. Do not use dynamic/generated class names as selectors, including Emotion class names. After adding anydata-testid— even a single attribute in one file — always rebuild the VSIX and reinstall it before rerunning steps:
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.
- 3d ago First seen · 155 lines · 38 tokens per session scan A 59ed0d0a71f0
ballerina-e2e-writer is a skill published in the GitHub repository ballerina-platform/ballerina-vscode (49 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 1,682 once invoked, about $0.0002 per session on Opus 5.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-10-26.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.