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/supply-chainnpx skills add padamson/playwright-rust --skill supply-chaingit clone --depth 1 https://github.com/padamson/playwright-rustWrote 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/padamson/playwright-rust/supply-chain)<a href="https://agentmods.dev/skills/padamson/playwright-rust/supply-chain"><img src="https://agentmods.dev/badge/skills/padamson/playwright-rust/supply-chain.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.00707 |
| Opus 5 | $0.00020 | $0.00353 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
supply-chain 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain & Release Hygiene
The project uses three complementary supply-chain tools:
cargo audit— vulnerability advisories from RustSeccargo deny— license, duplicate, and source policycargo vet— explicit audit chain for every dependency
All three run in CI on every push and every dependabot PR. Treat their
output as load-bearing — a real cargo audit failure is a security
advisory and warrants a patch release; a cargo vet failure usually
means an audit chain needs re-stitching after a version change.
When bumping our own version
supply-chain/imports.lock is generated, never hand-edited. The
header comment says # cargo-vet imports lock. The
[[unpublished.playwright-rs]] entries handle the chicken-and-egg
window between bumping Cargo.toml and publishing to crates.io: an
entry like version = "0.12.1" audited_as = "0.12.0" tells vet "treat
the in-tree version as audited at the prior released version's level."
Proper sequence when bumping Cargo.toml:
- Bump
version = "X.Y.Z"in workspaceCargo.toml - Run
cargo vet regenerate unpublished— automatically removes entries for now-published versions and adds a new[[unpublished]]entry chained to the prior version - If
cargo vetstill fails (the chain may break when prior versions get published and lose their[[unpublished]]placeholder), bump the[[exemptions.playwright-rs]] version = "..."line insupply-chain/config.tomlto the latest published version. The exemption is the anchor that the unpublished entries chain to. - Verify
cargo vet,cargo audit,cargo deny checkall pass - Commit
Cargo.toml,Cargo.lock,supply-chain/imports.lock, and anysupply-chain/config.tomlexemption bump together
When external dependencies update (dependabot PRs)
Dependabot PRs that bump external crates often surface "missing
[safe-to-deploy]" or "missing [safe-to-run]" failures from
cargo vet. Resolve by either:
- Running
cargo vet diff <crate> <old> <new>andcargo vet certifyto record an explicit audit (preferred for small, reviewable diffs), or - Adding an exemption in
supply-chain/config.toml(acceptable for well-known crates with negligible delta — match the existing exemption style).
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.
- 5d ago First seen · 65 lines · 41 tokens per session scan A 48f430c01eb5
supply-chain is a skill published in the GitHub repository padamson/playwright-rust (141 stars, last pushed 5d ago), licensed Apache-2.0. It adds 41 tokens to every session and 707 once invoked, about $0.0002 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-30.
Other skills, from other repositories
webcmd-browser
Use when a live browser task requires Playwright interaction, authenticated handoff, visible UI verification, or ad-hoc page inspection.
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.
opensteer
Direct browser control via CDP. Use when the user wants to automate, inspect, scrape, test, or interact with web pages.
apitap
ApiTap gives AI agents cheap access to web data through three layers.
auto-research
Research uncertain questions with an explicit, user-approved web search or ChatGPT consultation, then present options and wait for implementation approval.