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 SkiTemplar/ultron-control-center --skill webapp-testinggit clone --depth 1 https://github.com/SkiTemplar/ultron-control-centerWrote 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/skitemplar/ultron-control-center/webapp-testing)<a href="https://agentmods.dev/skills/skitemplar/ultron-control-center/webapp-testing"><img src="https://agentmods.dev/badge/skills/skitemplar/ultron-control-center/webapp-testing.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.1 | $0.00013 | $0.00191 |
| Opus 5 | $0.00006 | $0.00096 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
webapp-testing 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 7d 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.
What it actually says
Webapp-Testing — ULTRON Skill
This is a starter template for the webapp-testing skill. Edit freely.
When to use
(Describe the triggers this skill should match. Activate for interacting with and testing local web applications using Playwright — verifying frontend functionality, debugging UI behavior, capturing screenshots, or inspecting browser logs.)
Workflow
- (First step — launch Playwright and navigate to the local app URL.)
- (Second step — exercise the flow under test; capture evidence.)
- (Final output expectation — pass/fail report with screenshots + logs.)
Customize
This file lives at ~/.claude/skills/webapp-testing/SKILL.md. Modify it to
fit your workflow. The installer's manifest entry points here via
repo://skills/webapp-testing.
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.
- 7d ago First seen · 25 lines · 13 tokens per session scan A dcbf1b2d7f17
webapp-testing is a skill published in the GitHub repository SkiTemplar/ultron-control-center (1 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 191 once invoked, about $0.0001 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
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
excellence-review
Mandatory excellence gates for Grok+ACOS. verification-loop, santa-method, gstack-qa, plan-reviews, repo-mastery, cso, rules-distill. Never ship without evidence (gstack screenshots, metrics). Use on any build/suggest/lead task.
webapp-testing
Automated webapp testing with Playwright. Server management, UI testing, visual debugging, and reconnaissance-first approach.
test-web-ui
Automated web QA skill: analyzes a website or project, generates end-user use cases, derives a structured test plan, executes tests via Playwright browser automation, and produces a full HTML/Markdown QA report with screenshots and pass/fail results. TRIGGER this skill whenever the user asks to: test a website, run QA…