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 lovstudio/skills --skill runtime-verificationgit clone --depth 1 https://github.com/lovstudio/skillsWrote 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/lovstudio/skills/runtime-verification)<a href="https://agentmods.dev/skills/lovstudio/skills/runtime-verification"><img src="https://agentmods.dev/badge/skills/lovstudio/skills/runtime-verification/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/lovstudio/skills/runtime-verification"><img src="https://agentmods.dev/badge/skills/lovstudio/skills/runtime-verification.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.03733 |
| Opus 5.5 | $0.00016 | $0.01493 |
| Sonnet 5.5 | $0.00008 | $0.00747 |
| Haiku 4.5 | $0.00004 | $0.00373 |
Grade A, and why
lov-runtime-verification 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 20d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
性能实测 · Performance Verification
验证具体客户端 App 的修复是否在真实宿主链路中减少了目标工作，同时保留正确性、恢复语义和用户体验。把源码边界、项目门禁、内部工作量、运行时指标、用户体验和宿主生命周期分别报告；缺少同负载前后对照时诚实停在较低终态。
Triggers
Activate when
- 用户说“帮我验证这个客户端性能修复是否真的生效”“在真机上复测后台恢复”“确认 Web/PWA 修复在真实浏览器生命周期中有效”。
- 用户要求验收 IPC/RPC 批量化、lazy hydration、轮询降载、缓存、进程/线程、内存、终端/session 回收或宿主生命周期修复。
- The user asks to verify a runtime fix on an actual Electron/Tauri/native desktop build, iOS/Android device, React Native/Flutter app, or deployed Web/PWA in a real browser.
Do not activate when
- 用户还没有修复、基线或可复现工作负载；先调用
lov-runtime-audit建立证据。 - 用户只要求跑一次单测、lint、编译或 Lighthouse，不要求真实 runtime 因果验收；使用项目原生校验流程或对应专项工具。
- The request only predicts performance from source, benchmarks hardware, or treats a simulator screenshot as proof of a physical-device lifecycle claim.
Invocation and shared dependencies
invocation: kit_only。本模块不能作为自带全部依赖的 standalone Skill 调用。KIT_DIR必须解析为含kit.yaml的 App Optimizer Kit 根目录；SKILL_DIR只指当前skills/runtime-verification模块。- 共享契约和脚本一律从
$KIT_DIR/references/*与$KIT_DIR/scripts/*读取，不复制、不猜测本地替代物。 - 至少需要
$KIT_DIR/references/evidence-contract.md、$KIT_DIR/references/runtime-playbook.md、$KIT_DIR/references/platform-adapters.md、$KIT_DIR/scripts/evidence_report.py和$KIT_DIR/scripts/profile_store.py；缺失时输出blocked并列出缺口。 - 机器可读证据使用
app-runtime-evidence/v1；旧的 Electron 专用 schema 只能作为待迁移输入，不能作为新报告格式。
Kit-only I/O contract
Inputs
要求至少提供或现场解析：
platform_family、runtime、App/version/build/commit、构建模式和发布渠道；框架与宿主分开记录，例如mobile + react-native + ios、mobile + flutter + android。- baseline 的 metric definition、unit、process/thread/page boundary、workload、scale、sample window、sampler 与 provenance。
- 包含修复的真实产物及宿主：正在运行的 desktop build、安装到目标物理设备的 mobile build，或实际部署并由指定浏览器加载的 Web/PWA URL。
- 可复现触发事件与预先声明的阈值，至少覆盖一个用户体验指标和一个内部工作量或运行时指标。
- 项目要求的 format/lint/typecheck/test/build、平台签名/安装门禁，以及修复相关的 lifecycle、resume/restore 与数据保护不变量。
只有补丁和测试、没有实际 patched runtime 时，最高只能是 implemented_not_runtime_verified。已有部分真实运行证据但关键体验 A/B、目标生命周期或生产观察缺失时，最高只能是 partially_verified。
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago First seen · 198 lines · 40 tokens per session scan A 8a9298568a6e
lov-runtime-verification is a skill published in the GitHub repository lovstudio/skills (72 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 3,733 once invoked, about $0.0002 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-09-26.
Other skills, from other repositories
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…
debugging-livekit-agents
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it…
ui-regression
This skill should be used when the user asks to "verify UI changes", "test every screen and action", "run regression QA", "check a deployed UI", or "validate an extension release". Test known web and browser-extension workflows on localhost, staging, or production with action coverage, recovery, localization…
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.