Borrowing it
Nothing to install: this file belongs to posit-dev/py-shiny-site. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/posit-dev/py-shiny-site/main/.claude/skills/testing-example-apps/SKILL.mdgit clone --depth 1 https://github.com/posit-dev/py-shiny-siteWrote 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/posit-dev/py-shiny-site/testing-example-apps)<a href="https://agentmods.dev/skills/posit-dev/py-shiny-site/testing-example-apps"><img src="https://agentmods.dev/badge/skills/posit-dev/py-shiny-site/testing-example-apps/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/posit-dev/py-shiny-site/testing-example-apps"><img src="https://agentmods.dev/badge/skills/posit-dev/py-shiny-site/testing-example-apps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.01721 |
| Opus 5.5 | $0.00029 | $0.00688 |
| Sonnet 5.5 | $0.00015 | $0.00344 |
| Haiku 4.5 | $0.00007 | $0.00172 |
Grade A, and why
testing-example-apps 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 2mo 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Example Apps
Overview
Component example apps (components/**/app.py, components/**/app-*.py) are the source
of truth for each page — the shinylive links in index.qmd are generated from them. Smoke
coverage (it loads with no server, JS, or output errors) is centralized: a single
parametrized components/test_examples_smoke.py auto-discovers and smoke-tests every such app,
one test_example_app_smoke[<relative path>] case per app. This skill covers adding
py-shiny Playwright
interaction tests for the primary Core + Express apps via py-shiny's controllers — you
do not write per-component smoke tests.
Everything uses the public shiny package API — shiny.pytest.create_app_fixture,
shiny.playwright.controller, shiny.run.ShinyAppProc. No custom test runner.
Reference implementation: components/layout/accordion/test_accordion.py.
Shared infrastructure (already in place — do not re-create)
pytest.ini(repo root):testpaths = componentsscopes pytest to the site's tests and away from thepy-shiny/submodule.components/conftest.pyprovides:create_example_fixture(HERE / "app-NAME.py")— returns a fixture yielding a runningShinyAppProc. Splits multi-file## file:shinylive apps into a temp dir; launches single-file apps directly.smoke_testfixture — a callablesmoke_test(page, app, *, allow_stderr=(), allow_js=())that navigates, waits for Shiny idle, and asserts no un-allow-listed server stderr, no JS console errors, and zero.shiny-output-error.example_app_paths()/launch_example_app()— power the centralized smoke sweep below; you generally don't call these directly from a component'stest_<name>.py.
components/test_examples_smoke.py— smoke-tests EVERY discovered example app (app.py/app-*.py) as its own parametrized case; you do NOT write per-component smoke tests.components/test_component_pages.py— a static (non-browser) check that every component page (components/<section>/<name>/index.qmd) ships at least one example app (app.py/app-*.py). All discovered pages are enforced; a page may only opt out viaEXEMPT_PAGES(normally empty) with a documented reason. Runs undermake test-components-examples.
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.
- 2mo ago First seen · 123 lines · 73 tokens per session scan A 3382348638e1
testing-example-apps is a skill published in the GitHub repository posit-dev/py-shiny-site (22 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,721 once invoked, about $0.0003 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-30.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…