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 korbinjoe/TeemAI --skill render-performance-verificationgit clone --depth 1 https://github.com/korbinjoe/TeemAIWrote 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/korbinjoe/teemai/render-performance-verification)<a href="https://agentmods.dev/skills/korbinjoe/teemai/render-performance-verification"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/render-performance-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/korbinjoe/teemai/render-performance-verification"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/render-performance-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.00038 | $0.00633 |
| Opus 5.5 | $0.00015 | $0.00253 |
| Sonnet 5.5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
render-performance-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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Render Performance Verification
Use this skill after UI-impacting work where render speed, mission switching, terminal restoration, or route readiness could regress.
This skill also installs an automatic Stop hook. At the end of an agent turn,
the hook detects changed code files, fingerprints their current contents, and
runs npm run build:ui plus npm run perf:render:changed once for each new
fingerprint. Set TEEMAI_RENDER_PERF_AUTO=0 to disable it locally.
Trigger
Run this for changes under:
web/components/**web/hooks/useChat*,web/hooks/useAgent*,web/hooks/useWorkspace*web/layouts/**,web/pages/**,web/App.tsxweb/**/*.cssor theme/layout files- server/WebSocket/API behavior that changes UI rendering or live mission state
Workflow
-
Run the normal build gate unless it already passed in the same task:
npm run build:ui -
Run changed-scope render verification:
npm run perf:render:changed -
If a scenario fails, rerun the failing scenario with trace artifacts:
npm run perf:render -- --scenario <scenario-id> --trace --keep-artifacts -
Read
.perf/render/<run-id>/report.mdand inspect the first failing scenario'smetrics.json, screenshot, and trace path. -
Fix the regression and rerun the relevant scenario or
perf:render:changed.
Harness Self-Check
If the failure evidence points to the harness itself, treat it as a harness regression and fix it before trusting the result. Common signs:
- selector strict-mode errors or missing selectors after a UI label changed
- a metric that is known to include detached or garbage-collection-sensitive browser state
- a changed-file mapping that misses an obviously impacted surface
- a scenario that flakes while screenshots, console, network, and interaction metrics are otherwise healthy
Do not bypass the scenario or update baselines for these cases. Patch the
harness, add or update the focused test when practical, then rerun the failing
scenario and npm run perf:render:changed.
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.
- 1mo ago First seen · 87 lines · 38 tokens per session scan A ace36b1dfed2
render-performance-verification is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 633 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-08-31.
Other skills, from other repositories
azure-app-testing
Expert knowledge for Azure App Testing development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when running Azure Load Testing, Playwright Workspaces, JMeter/Locust tests…
azure-chaos-studio
Expert knowledge for Chaos Studio development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when automating Chaos Studio via CLI/ARM, configuring AKS pod faults, securing Private Link/RBAC, or choosing…
azure-devtest-labs
Expert knowledge for Azure DevTest Labs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing lab VM images, ARM/CI-CD automation, RBAC/Key Vault security…
azure-playwright-workspaces
Expert knowledge for Playwright Workspaces development including troubleshooting, best practices, decision making, limits & quotas, security, and configuration. Use when managing Playwright Testing workspaces, tokens/RBAC, quotas, monitoring/metrics, or run/AADSTS7000112 issues, and other Playwright Workspaces related…
azure-test-plans
Expert knowledge for Azure Test Plans development including limits & quotas, security, configuration, and integrations & coding patterns. Use when configuring test failure types, custom fields, retention, permissions, or tcm.exe-based test suite automation, and other Azure Test Plans related development tasks. Not for…
failure-path-review
A review tool for checking how a service method handles failures. It compares the method's error branches with documented failure paths and their tests.