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 skills add alphabravo-oss/guild --skill authorgit clone --depth 1 https://github.com/alphabravo-oss/guildWrote 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/alphabravo-oss/guild/author)<a href="https://agentmods.dev/skills/alphabravo-oss/guild/author"><img src="https://agentmods.dev/badge/skills/alphabravo-oss/guild/author/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/alphabravo-oss/guild/author"><img src="https://agentmods.dev/badge/skills/alphabravo-oss/guild/author.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.00061 | $0.01418 |
| Opus 5.5 | $0.00024 | $0.00567 |
| Sonnet 5.5 | $0.00012 | $0.00284 |
| Haiku 4.5 | $0.00006 | $0.00142 |
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 1mo 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 — 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:
page.getByRole(role, { name })— matches accessibility tree. Survives most refactors.page.getByLabel(text)— for form fields with<label>association.page.getByText(text, { exact })— for prose, headings, links by visible text.page.getByTestId(id)— only if the team usesdata-testidand is committed to keeping them stable.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 appearawait expect(locator).toHaveText(value)— wait for the content to settleawait page.waitForURL(predicate)— wait for navigationawait 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 () => {
// ...
});
});
});
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.
- 1mo ago First seen · 126 lines · 61 tokens per session scan A 4a5526f8117a
author is a skill published in the GitHub repository alphabravo-oss/guild (3 stars, last pushed 19d ago), licensed MIT. It adds 61 tokens to every session and 1,418 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-08-31.
Other skills, from other repositories
playwright-e2e-test
Writes end-to-end browser tests in TypeScript with @playwright/test for any web UI that is not Vaadin (Angular today, other client-side frameworks alike): a use case test (UC-XXX) with one test per scenario, or a test case journey (TC-XXX) that walks the whole Flow table across views with one test.step per row.…
typescript-e2e-testing
E2E and integration testing for TypeScript/NestJS projects using Jest, supertest, and real infrastructure via Docker (Kafka, PostgreSQL, MongoDB, Redis) with the Given-When-Then pattern. Use whenever the user is working on .e2e-spec.ts files or anything under test/e2e/, or asks to set up, write, review, run, debug, or…
compiler
Use when converting a refined markdown E2E test case into a standard Playwright .spec.ts file. Triggers on "compile this test", "convert to playwright", or "generate spec from markdown". Requires a stable markdown test case and a running dev server.
e2e-test-conventions
Core conventions and rules for Playwright E2E testing with TypeScript. Covers project structure, naming conventions, selector strategy, authentication, navigation, environment configuration, test independence, and parallelism. Automatically loaded when writing or modifying E2E tests. Use when: generating E2E tests…
automated_qa_cypress
Use when user needs Cypress E2E test specs written in TypeScript using Page Object Model with CI/CD integration.
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.