author

author is a skill for Claude Code, Codex from alphabravo-oss/guild. It costs 61 tokens per session (1,418 once invoked), scanned A, original, MIT.

A set of rules for writing Playwright end-to-end test files in TypeScript. It covers reliable element selection, waiting for page actions, reusable test setup, and readable test traces.

In plain words
What is it for?
It is for creating or changing Playwright tests through the listed end-to-end testing commands and writer agent.
Why use it?
It helps prevent tests from failing intermittently because they depend on fragile selectors, fixed delays, or setup that leaves behind old data.

Skill for Claude CodeCodex

Part of the e2e plugin — 2 skills, 6 commands, 1 agent shipped together

Install

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.

agentmods
npx agentmods add skills/alphabravo-oss/guild/author
Any agent
npx skills add alphabravo-oss/guild --skill author
Clone the repo
git clone --depth 1 https://github.com/alphabravo-oss/guild

Made for: Claude Code, Codex.

Or install e2e, the plugin that ships this one along with the rest of its 2 skills, 6 commands, 1 agent.

Wrote 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.

agentmods badge for author

README.md
[![agentmods](https://agentmods.dev/badge/skills/alphabravo-oss/guild/author.svg)](https://agentmods.dev/skills/alphabravo-oss/guild/author)
Your own site
<a href="https://agentmods.dev/skills/alphabravo-oss/guild/author"><img src="https://agentmods.dev/badge/skills/alphabravo-oss/guild/author.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,418 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.01418
Opus 5 $0.00030 $0.00709
Sonnet 5 $0.00012 $0.00284
Haiku 4.5 $0.00006 $0.00142

Measured 3d ago against content hash 4a5526f8117a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

author 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.

plugins/e2e/skills/author/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

e2e:author — Playwright Spec Authoring Rules

You are about to write or modify a Playwright spec. These rules are non-negotiable unless the user explicitly overrides one — they encode lessons that took the Playwright community years to learn.

1. Locators

Priority order — use the first that works:

  1. page.getByRole(role, { name }) — matches accessibility tree. Survives most refactors.
  2. page.getByLabel(text) — for form fields with <label> association.
  3. page.getByText(text, { exact }) — for prose, headings, links by visible text.
  4. page.getByTestId(id) — only if the team uses data-testid and is committed to keeping them stable.
  5. page.locator('css') — last resort. Comment why nothing above worked.

Never:

  • XPath (unless wrapping a known-stable third-party widget)
  • CSS class names that look like Tailwind/utility classes (.bg-blue-500) — they're transient
  • Nth-child indexing into a list without anchoring on a sibling's text

Always:

  • Chain locators when the element is inside a known parent: page.getByRole('navigation').getByRole('link', { name: 'Pricing' }). This survives a copy of the same locator appearing elsewhere on the page.
  • Use { exact: true } on text matches when partial matches would be ambiguous.

2. Waits

Never write page.waitForTimeout(ms). It is always wrong. Replace with one of:

  • await expect(locator).toBeVisible({ timeout }) — wait for the element to appear
  • await expect(locator).toHaveText(value) — wait for the content to settle
  • await page.waitForURL(predicate) — wait for navigation
  • await page.waitForResponse(url) — wait for a specific API call

Auto-wait is built into expect() against locators — await expect(page.getByRole('button')).toBeEnabled() polls until true or times out. Use it.

The only exception: a documented animation that has no observable end state (no class change, no aria-hidden flip). In that case, comment WHY the timeout is unavoidable.

3. Structure

import { test, expect } from '@playwright/test';

test.describe('<feature or page>', () => {
  test.beforeEach(async ({ page }) => {
    // common setup (navigation, auth state already set via storageState)
  });

  test('<specific behavior>', async ({ page }) => {
    await test.step('<human-readable step>', async () => {
      // ...
    });

    await test.step('<next step>', async () => {
      // ...
    });
  });
});

Read the full file on GitHub · 126 lines

Changes

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.

  1. 3d ago First seen · 126 lines · 61 tokens per session scan A 4a5526f8117a

Subscribe to this mod's changes

author is a skill published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 4d ago), licensed MIT. It adds 61 tokens to every session and 1,418 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

verify

Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.

Hmbown/CodeWhale · 25 tokens

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.

callstack/agent-device · 55 tokens

local-frontend-check

Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.

ascending-llc/jarvis-registry · 52 tokens

pr-integration-test

Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.

microsoft/intelligent-terminal · 66 tokens

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.

warpdotdev/warp · 55 tokens