vscode-gitlens: Skill for Claude Code

.claude/skills/add-test/SKILL.md

add-test is a skill for Claude Code from gitkraken/vscode-gitlens. It costs 14 tokens per session (1,269 once invoked), scanned A, original, no licence file.

A generator for unit tests and end-to-end tests for code that already exists.

In plain words
What is it for?
It helps add tests around existing code, including tests for individual units and tests that check complete user flows.
Why use it?
It removes the need to create these test files and their initial structure by hand.

Skill for Claude Code ✓ vendor

Written for Claude Code: installed under .claude/.

This is gitkraken/vscode-gitlens's own configuration. It tells Claude Code how to work on vscode-gitlens 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-gitlens configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gitkraken/vscode-gitlens. 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/gitkraken/vscode-gitlens/main/.claude/skills/add-test/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/gitkraken/vscode-gitlens

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 add-test

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gitkraken/vscode-gitlens/add-test"><img src="https://agentmods.dev/badge/skills/gitkraken/vscode-gitlens/add-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,269 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 unknown 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.00014 $0.01269
Opus 5.5 $0.00006 $0.00508
Sonnet 5.5 $0.00003 $0.00254
Haiku 4.5 $0.00001 $0.00127

Measured 1mo ago against content hash e08306a2006f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

add-test 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.

.claude/skills/add-test/SKILL.md · 179 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 1mo ago Changed e08306a2006f
  2. 2mo ago First seen · 179 lines · 14 tokens per session scan A 950d3f507652

Subscribe to this mod's changes

add-test is a skill published in the GitHub repository gitkraken/vscode-gitlens (9,958 stars, last pushed today), with no licence file. It adds 14 tokens to every session and 1,269 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

vscode-visual-regression

Write Storybook stories and visual regression tests for the Kilo VS Code extension webview UI.

Kilo-Org/kilocode · 25 tokens

pr-track-v1

Create a GitHub tracking issue in Kilo-Org/kilocode that captures a merged Kilo v1 PR's behavior so it can be re-implemented or verified in opencode v2. Use when the user invokes /pr-track-v1 or asks to track a v1 core fix/feature for the v2 rewrite.

Kilo-Org/kilocode · 72 tokens

kilocode-merge-minimizer

Use when changing shared upstream-owned files to add Kilo-specific behavior, editing kilocodechange markers in shared code, or moving additive behavior out of shared code to reduce upstream merge conflicts. Do not use for changes confined to Kilo-owned paths such as packages/kilo-vscode/ or packages/kilo-ui/.

Kilo-Org/kilocode · 76 tokens

backseat-driver-testing

Testing strategies for Calva Backseat Driver MCP tools. Use when: Testing Backseat Driver, validating tool updates, testing structural editing workflows, verifying REPL evaluation with who-tracking, testing shadow-cljs runtime discovery and targeting, testing output log filtering, testing load-file tool, smoke testing…

BetterThanTomorrow/calva-backseat-driver · 106 tokens

github-release-management

GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.

frankxai/claude-skills-library · 43 tokens

wait-for-pr-checks

Poll a GitHub PR's checks until they all pass, any one fails, or a timeout is hit. Returns a structured outcome the caller can gate on. TRIGGER when the user says "wait for CI", "wait for the PR checks", "watch the PR", "is CI green yet", "babysit this PR's checks", "block until checks pass"…

thettwe/nyann · 148 tokens