Borrowing it
Nothing to install: this file belongs to spences10/sveltest. 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/spences10/sveltest/main/.agents/skills/svelte-testing/SKILL.mdgit clone --depth 1 https://github.com/spences10/sveltestWrote 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/spences10/sveltest/svelte-testing)<a href="https://agentmods.dev/skills/spences10/sveltest/svelte-testing"><img src="https://agentmods.dev/badge/skills/spences10/sveltest/svelte-testing/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/spences10/sveltest/svelte-testing"><img src="https://agentmods.dev/badge/skills/spences10/sveltest/svelte-testing.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.00049 | $0.00588 |
| Opus 5.5 | $0.00020 | $0.00235 |
| Sonnet 5.5 | $0.00010 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
svelte-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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Svelte Testing
Quick Start
// Client-side component test (.svelte.test.ts)
import { render } from 'vitest-browser-svelte';
import { expect } from 'vitest';
import Button from './button.svelte';
test('button click increments counter', async () => {
const page = await render(Button);
const button = page.getByRole('button', { name: /click me/i });
await button.click();
await expect.element(button).toHaveTextContent('Clicked: 1');
});
Core Principles
- Always use locators:
page.getBy*()methods, never containers - Multiple elements: Use
.first(),.nth(),.last()to avoid strict mode violations - Use untrack(): When accessing
$derivedvalues in tests - Real API objects: Test with FormData/Request, minimal mocking
Reference Files
- core-principles | foundation-first | client-examples
- server-ssr-examples | critical-patterns
- client-server-alignment | troubleshooting
Notes
- In component tests, test form state without submitting SvelteKit
forms; use
await expect.element()for locator assertions - In Playwright E2E, submit real forms and use
await expect(locator) - Colocate
.svelte.test.ts(client),.test.ts(Node),.ssr.test.ts(optional SSR), and.e2e.ts(Playwright) - CLI baseline:
client/serverprojects and assertion enforcement; Playwright matches**/*.e2e.{ts,js} - Import
pagefromvitest/browser; awaitrenderwith renderer v3 - Importing
renderregisters cleanup without a setup file
What ships with it
8 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.
- 1mo ago Changed · +5 lines 80e091de63f5
- 2mo ago First seen · 59 lines · 49 tokens per session scan A f5f871419c07
svelte-testing is a skill published in the GitHub repository spences10/sveltest (113 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 588 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-30.
Other skills, from other repositories
praman-sap-cli
SAP UI5 test automation via Playwright CLI. Use when testing SAP Fiori apps, discovering UI5 controls, debugging Praman tests, or automating SAP workflows. Extends playwright-cli with SAP/UI5 awareness.
svelte5-runes-static
Svelte 5 runes + SvelteKit adapter-static (SSG/SSR) patterns for hydration-safe state, store bridges, and reactivity that survives prerendering.
svelte5-runes-static
Svelte 5 runes + SvelteKit adapter-static (SSG/SSR) patterns for hydration-safe state, store bridges, and reactivity that survives prerendering.
playwright-e2e-testing
Use this skill when writing, debugging, or maintaining Playwright end-to-end tests in TypeScript, JavaScript, or Python. Covers test structure and architecture (Page Object Model, fixtures, custom matchers), locator strategy (role-based, test-ID, accessible selectors), auto-waiting and retry, API/network mocking…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).