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/lfyxhappy/lfcode/playwright-browsernpx skills add lfyxhappy/lfcode --skill playwright-browsergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWhat 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.00042 | $0.00482 |
| Opus 5 | $0.00021 | $0.00241 |
| Sonnet 5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
playwright-browser 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 yesterday.
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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lfcode Playwright Browser
Use this skill whenever the task involves Playwright MCP browser tools such as browser_navigate, browser_snapshot, browser_click, browser_type, or screenshots in the Lfcode desktop app.
Target
Lfcode desktop has an embedded side browser implemented as an Electron <webview>. It uses the persistent partition persist:lfcode-browser.
Playwright automation must target that embedded side browser. Do not navigate, reload, or otherwise replace the Electron app shell window.
Workflow
- Treat the Lfcode main window as the application shell, not the browser target.
- Before navigating, look for an existing embedded side browser target first. A collapsed, hidden, inactive,
inert, ordisplay:noneside browser still counts as open when its browser tab or webview target exists. - Reuse the existing side browser target when it exists. Do not create duplicate browser tabs just because the side panel is hidden.
- Create or open a side browser tab only when no embedded browser target exists.
- Use Playwright browser tools only for the actual web page inside the side browser.
- After navigation or major UI changes, take a fresh snapshot before clicking element references.
- If a hidden side browser target is selected but cannot produce a useful snapshot or interaction, bring the side browser panel/tab active, then continue on the same target.
- If a Playwright action appears to affect the whole Lfcode window, stop using that tab and reopen or retarget the embedded side browser before continuing.
Guardrails
- Never call
browser_navigateagainst the Electron main app shell. - Never use Playwright to replace the Lfcode UI with an external website.
- External web pages belong in the side browser panel.
- If multiple pages or targets are visible, choose the target that corresponds to the embedded browser webview, not the
Lfcodeapplication page. - Hidden side browser targets are valid targets; closed browser tabs are not.
- If you are unsure which target is current, list tabs or inspect a snapshot before taking navigation actions.
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.
- yesterday First seen · 35 lines · 42 tokens per session scan A 7cf361f4a839
playwright-browser is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 482 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-31.
Other skills, from other repositories
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
Implement (multi-agent loop)
Orchestrate an implement -> review -> fix loop with subagents until reviewers sign off.
Best of N (parallel attempts)
Delegate N parallel subagents on the same task, then pick the best result.
Check work (verify against criteria)
Verify an implementation against acceptance criteria with a reviewer and a tester.
Commit (clean, conventional)
Stage the right changes and write a clear, conventional commit message.
Design doc (write -> review loop)
Draft a design document and iterate writer/reviewer subagents until consensus.