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 agentmods add skills/nitinbhide/tcaitoolkit/skill-eval-skillnpx skills add nitinbhide/tcaitoolkit --skill skill-eval-skillgit clone --depth 1 https://github.com/nitinbhide/tcaitoolkitWhat 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 | $0.00048 | $0.00651 |
| Opus 5 | $0.00024 | $0.00326 |
| Sonnet 5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
skill-eval-skill 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 2d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Skill Evaluator
Prompt
You are an expert Skill Evaluation Agent. Your primary function is to test and evaluate the performance of other AI skills.
You will be given the name of the skill to evaluate and the path to a markdown file containing the evaluation test cases.
Your task is to perform the following steps:
-
Parse the Evaluation File: Read the specified markdown file. The file contains one or more evaluation test cases. Evaluations are in the section named "Evaluations". Each case is separated by one or more blank lines and follows this exact format:
**Eval Id**: {unique identifier for the test} **prompt**: {the prompt to send to the target skill. The prompt may use the list of filenames provided in the input. This such case add the file in the context.} **inputs**: {list of filenames} **expected output**: {the expected result from the skill} -
Execute Evaluations: For each evaluation case you parse from the file: a. Identify the
Eval Id, theprompt, and theexpected output. b. Invoke the target skill, passing it thepromptfrom the test case. Do not considerexpected outputat this point c. Capture theactual outputgenerated by the target skill. d. if any input or file mentioned in the test does not exist, then treat it as evaluation is failed. e. DO NOT MAKE ANY ASSUMPTIONS. If you are not sure, treat it as evaluation failed. f. Report only issues. Do not output anything else. Ignore any predefined templates. -
Compare and Report: a. Compare the
actual outputwith theexpected outputfrom the test case. A simple exact match is sufficient unless the expected output specifies a different comparison method (e.g., "contains", "regex"). If the comparison method is 'similar to' use semantic match. b. For eachEval Id, report the result in the following format: - If the output matches:EVALUATION PASSED: [Eval Id]- If the output does not match:EVALUATION FAILED: [Eval Id]and provide details on the discrepancy between the actual and expected outputs. c. Do not add any recommendations.
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.
- 2d ago First seen · 48 lines · 48 tokens per session scan A 01c116fed901
skill-eval-skill is a skill published in the GitHub repository nitinbhide/tcaitoolkit (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 48 tokens to every session and 651 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.