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/padamson/playwright-rust/release-processnpx skills add padamson/playwright-rust --skill release-processgit clone --depth 1 https://github.com/padamson/playwright-rustWhat 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.00058 | $0.03782 |
| Opus 5 | $0.00029 | $0.01891 |
| Sonnet 5 | $0.00012 | $0.00756 |
| Haiku 4.5 | $0.00006 | $0.00378 |
Grade A, and why
release-process scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s https://index.crates.io/pl/ay/playwright-rs | tail -1` How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Process
This skill captures the procedural steps for shipping a playwright-rust release. For deeper automation (full pre-flight checks, mutation testing, CHANGELOG validation), use the release-preparation sub-agent. This skill exists for in-context reference when you're walking through a release manually or guiding the user.
Workspace layout — three independently-versioned crates
Three publishable crates, each with its own CHANGELOG and tag prefix:
| Crate | Path | CHANGELOG | Tag prefix |
|---|---|---|---|
playwright-rs |
crates/playwright/ |
crates/playwright/CHANGELOG.md |
vX.Y.Z |
playwright-rs-macros |
crates/playwright-rs-macros/ |
crates/playwright-rs-macros/CHANGELOG.md |
macros-vX.Y.Z |
playwright-rs-trace |
crates/playwright-rs-trace/ |
crates/playwright-rs-trace/CHANGELOG.md |
trace-vX.Y.Z |
The top-level CHANGELOG.md is an index file, not a changelog —
release notes are generated per-crate from each crate's own CHANGELOG.
The xtask workspace member is publish = false and has no CHANGELOG;
its workflow is documented in crates/xtask/.
Versioning
0.x.y— pre-1.0, API may change (current stage)1.0.0— stable API, ready for production- Patch (
x.y.Z) — bug fixes, security advisories, no API changes - Minor (
x.Y.0) — additive features, deprecations, no breaking changes permitted in 1.x but acceptable in 0.x - Major (
X.0.0) — breaking changes (post-1.0)
Security advisories against transitive deps always warrant a patch release, even if functional behavior is unchanged. See the supply-chain skill.
Pre-release checklist
Steps below assume you're releasing playwright-rs (the main crate).
For the macros or trace crate, swap the paths and tag prefix per the
table above; the workflow is otherwise identical.
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 · 278 lines · 58 tokens per session scan A acd385eb8ae0
release-process is a skill published in the GitHub repository padamson/playwright-rust (141 stars, last pushed 2d ago), licensed Apache-2.0. It adds 58 tokens to every session and 3,782 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
moli-webfetch
Fetch, inspect, crawl, and capture live, JavaScript-rendered websites with Moli. Use when Codex needs current web content, web research, fact lookup, link following, a bounded crawl, client-rendered or response-gated content, network diagnostics, or a standalone HTML, Markdown, JSON, semantic-tree, viewport or…
moli-cdp-server
Start Moli's CDP server and connect Playwright, Puppeteer, or raw CDP clients. Use to run a headless-browser CDP endpoint, replace a Chromium process, attach over CDP, enable real layout and screenshot surfaces, or diagnose CDP discovery, connection, and target startup—even when Moli is not named.
webcmd-browser
Use when a live browser task requires Playwright interaction, authenticated handoff, visible UI verification, or ad-hoc page inspection.
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
active-research
Deep research and analysis tool. Generates comprehensive HTML reports on any topic, domain, paper, or technology. Enhanced with advanced browser automation — SPA handling, network idle wait, batch operations, stealth browsing, and intelligent page analysis. Use when user asks to research, analyze, investigate…
deep-research
Deep research and analysis tool. Generates comprehensive HTML reports on any topic, domain, paper, or technology. Use when user asks to research, analyze, investigate, deep-dive, or generate a report on any subject. Supports academic papers (arXiv), technologies, trends, comparisons, and general topics.