vscode-sidebar-terminal: Skill for Claude Code

.claude/skills/vscode-test-setup/SKILL.md

vscode-test-setup is a skill for Claude Code from s-hiraoku/vscode-sidebar-terminal. It costs 61 tokens per session (4,068 once invoked), scanned A, original, MIT.

A setup guide for automated tests in Visual Studio Code extension projects. It explains how to configure Vitest, VS Code test tools, code coverage, and continuous integration pipelines.

In plain words
What is it for?
Use it to start or change a test setup, run extension tests in CI, measure which code tests cover, and improve test execution.
Why use it?
It removes the guesswork from creating a test environment and helps diagnose test configuration problems.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: $skill-name invocation.

This is s-hiraoku/vscode-sidebar-terminal's own configuration. It tells Claude Code how to work on vscode-sidebar-terminal itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vscode-sidebar-terminal configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is file: ./coverage/lcov.info.

Reuse

Borrowing it

Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/skills/vscode-test-setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminal

Made for: Claude Code.

Wrote 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.

agentmods badge for vscode-test-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/vscode-test-setup/github.svg)](https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/vscode-test-setup)
Your own site
<a href="https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/vscode-test-setup"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/vscode-test-setup/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.

agentmods 80×15 button for vscode-test-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/vscode-test-setup"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/vscode-test-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,068 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.04068
Opus 5 $0.00030 $0.02034
Sonnet 5 $0.00012 $0.00814
Haiku 4.5 $0.00006 $0.00407

Measured 6d ago against content hash ff2f218820d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

vscode-test-setup 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 6d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/setup-test-env.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/vscode-test-setup/SKILL.md · 665 lines

How it starts

The opening of the file, as written. The whole thing — 665 lines — stays where its author put it; the contents beside it link to each section on GitHub.

VS Code Extension Test Environment Setup

Overview

This skill enables rapid and reliable test environment setup for VS Code extension projects. It covers test framework configuration, CI/CD integration, coverage tooling, and best practices for maintainable test infrastructure.

When to Use This Skill

  • Setting up test infrastructure for new VS Code extension projects
  • Migrating from one test framework to another
  • Configuring CI/CD pipelines for extension testing
  • Setting up code coverage tools and thresholds
  • Troubleshooting test configuration issues
  • Optimizing test execution performance

Quick Start Setup

Step 1: Install Dependencies

# Core testing dependencies
npm install --save-dev \
  vitest \
  @vscode/test-cli \
  @vscode/test-electron

# Coverage is built into Vitest (uses v8 or c8 provider)
# No additional coverage packages needed

Step 2: Create Test Configuration

Run the setup script to create all necessary configuration files:

# Execute from skill directory
python scripts/setup-test-env.py --project-path /path/to/extension

Or manually create the following files:

vitest.config.ts
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    globals: true,
    environment: 'node',
    include: ['src/test/unit/**/*.test.ts'],
    coverage: {
      provider: 'v8',
      include: ['src/**/*.ts'],
      exclude: ['src/test/**', '**/*.d.ts'],
      reporter: ['text', 'html', 'lcov'],
      thresholds: {
        branches: 80,
        functions: 80,
        lines: 80,
        statements: 80
      }
    },
    testTimeout: 20000,
    retry: process.env.CI ? 2 : 0
  }
});
tsconfig.test.json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "module": "ESNext",
    "moduleResolution": "bundler",
    "outDir": "./out/test",
    "rootDir": "./src",
    "types": ["vitest/globals", "node"]
  },
  "include": [
    "src/test/**/*.ts"
  ]
}

Read the full file on GitHub · 665 lines

Files

What ships with it

2 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.

Changes

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.

  1. 6d ago First seen · 665 lines · 61 tokens per session scan A ff2f218820d2

Subscribe to this mod's changes

vscode-test-setup is a skill published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 4,068 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories

cloudflare-workers-testing

Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.

secondsky/claude-skills · 57 tokens

Code Coverage Analysis

Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.

PramodDutta/qaskills · 45 tokens

code-qualities-assessment

Assess code maintainability through 5 foundational qualities (cohesion, coupling, encapsulation, testability, non-redundancy) with quantifiable scoring rubrics. Works at method/class/module levels across multiple languages. Produces markdown reports with remediation guidance. Use when you ask to "assess…

rjmurillo/ai-agents · 108 tokens

qa-ci-cd-testing

Guidance for adding automated tests to a CI/CD pipeline, the process that checks and delivers software changes.

Kokxi/qa-test-skills · 135 tokens

wordpress-testing-qa

WordPress plugin and theme testing with PHPUnit integration tests, WPMock unit tests, PHPCS coding standards, and CI/CD workflows.

bobmatnyc/claude-mpm-skills · 31 tokens

jenkins-groovy-scripting-best-practices

Covers writing safe, testable Groovy inside Jenkins pipelines and shared libraries — the script security sandbox and approval workflow, unit testing with JenkinsPipelineUnit, CPS (Continuation-Passing Style) quirks, and common Groovy pitfalls specific to the pipeline execution context. Use when the user hits "script…

selvarajmurugesan90/ops-engineering-skills · 116 tokens