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 keska-labs/enterprise-skills --skill extension-test-patternsgit clone --depth 1 https://github.com/keska-labs/enterprise-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/keska-labs/enterprise-skills/extension-test-patterns)<a href="https://agentmods.dev/skills/keska-labs/enterprise-skills/extension-test-patterns"><img src="https://agentmods.dev/badge/skills/keska-labs/enterprise-skills/extension-test-patterns/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/keska-labs/enterprise-skills/extension-test-patterns"><img src="https://agentmods.dev/badge/skills/keska-labs/enterprise-skills/extension-test-patterns.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.00044 | $0.00496 |
| Opus 5 | $0.00022 | $0.00248 |
| Sonnet 5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
extension-test-patterns 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 11d 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
Extension test patterns
Two runners
| Runner | Entry | Use for |
|---|---|---|
| Jest | npm test / task test |
Services, utilities, React components (jsdom) |
| @vscode/test-electron | npm run test:extension / task test-extension |
Real Extension Host: activation, commands, webviews |
Jest configuration
vscodemock:"^vscode$": "<rootDir>/src/test/vscodeMock.ts"— extension code importingvscodegets the mock automatically.- CSS mock: maps to
src/test/styleMock.ts. src/test/suite/excluded — those files are Mocha suites for the extension host, not Jest.
Setup: src/test/setupTests.ts pulls in @testing-library/jest-dom.
Extension-host runner
src/test/runExtensionTests.ts resolves the repo root and loads src/test/suite/index. Use this path when debugging “tests pass in Jest but fail in real VS Code.”
When to extend vscodeMock
Prefer updating src/test/vscodeMock.ts when multiple tests need the same API surface (e.g. new workspace.fs behavior). Keeps mocks consistent and avoids duplicated jest.mock blocks.
Quick checklist for new code
- Pure logic / axios / parsers → Jest file next to source or under
src/test/*.test.ts. - React presentational / hooks with injected API → Jest + Testing Library in
webview-ui/*.test.tsx. - End-to-end extension behavior →
src/test/suite/.
Commands
task test # or npm test
task test-extension # or npm run test:extension
task check # full gate before release
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.
- 11d ago First seen · 49 lines · 44 tokens per session scan A c5ccaf2c5dc6
extension-test-patterns is a skill published in the GitHub repository keska-labs/enterprise-skills (7 stars, last pushed 22d ago), licensed MIT. It adds 44 tokens to every session and 496 once invoked, about $0.0002 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
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
unit-test-parameterized
Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value…