Borrowing it
Nothing to install: this file belongs to couimet/rangeLink. 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/couimet/rangeLink/main/.claude/skills/tcs-definition/SKILL.mdgit clone --depth 1 https://github.com/couimet/rangeLinkWrote 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/couimet/rangelink/tcs-definition)<a href="https://agentmods.dev/skills/couimet/rangelink/tcs-definition"><img src="https://agentmods.dev/badge/skills/couimet/rangelink/tcs-definition/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/couimet/rangelink/tcs-definition"><img src="https://agentmods.dev/badge/skills/couimet/rangelink/tcs-definition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 116 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00041 | $0.03080 |
| Opus 5 | $0.00020 | $0.01540 |
| Sonnet 5 | $0.00008 | $0.00616 |
| Haiku 4.5 | $0.00004 | $0.00308 |
Grade A, and why
tcs-definition 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 10d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TCs Definition
Interview-driven definition of new QA test cases for the current issue. Two-phase: draft into a /note for review/iteration, then on approval auto-insert into packages/rangelink-vscode-extension/qa/qa-test-cases.yaml.
Shared schema contract: the QA YAML schema (section headers, indentation, label format, automated: value vocabulary) is governed by CLAUDE.md § qa-yaml rules QA001-QA008. Both this skill and the tc-implement agent rely on those rules.
Input: Zero-argument for the draft phase, or the single-word subcommand apply to re-read an existing draft note and prompt for approval again (after the user has edited the note). The bare word — not --apply — keeps the slash invocation /tcs-definition apply short to type.
Step 1: Resolve Issue Context
Run in parallel:
git branch --show-current
gh issue view <issue-url-from-branch> --json title,body,number,state,labels
Extract the issue ID from issues/<ID> on the current branch. If the branch does not match issues/*, STOP with: STOP: tcs-definition runs on an issues/<ID> branch. Current branch is <name>. Switch to the issue branch and re-invoke. Read the active-plan note at the path stored in .claude-work/issues/<ID>/active-plan. If that pointer is missing, STOP with: STOP: No active-plan pointer at .claude-work/issues/<ID>/active-plan. Run /start-issue first.
If the issue body references a parent (e.g., Parent Issue: #47), fetch it via gh issue view.
Step 2: Read QA YAML and Existing Tests
Read in parallel:
packages/rangelink-vscode-extension/qa/qa-test-cases.yaml— the full file.- Glob
packages/rangelink-vscode-extension/src/__integration-tests__/suite/*.test.tsand scan for existingtest('<slug>-NNN:IDs. Build a slug → existing-IDs map.
Record the highest -NNN per feature slug; the skill uses max + 1 for new entries (per QA004 in CLAUDE.md).
Step 3: Read the Partial Diff (Optional Signal)
Run:
git diff <base-branch>...HEAD -- packages/rangelink-vscode-extension/src/
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.
- 10d ago First seen · 268 lines · 41 tokens per session scan A cb6abcf98dbc
tcs-definition is a skill published in the GitHub repository couimet/rangeLink (10 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 3,080 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
browser-qa-delivery
Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.
omh-agent-evaluation
This is a Hermes-native agent-evaluation workflow skill.
omh-verification-gate
This is a Hermes-native verification-gate workflow skill.
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
test-generator
Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.
skill-creator
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests. Use when authoring a new skill, repairing an existing skill, or measuring whether its metadata routes correctly.