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/version-control-skillnpx skills add nitinbhide/tcaitoolkit --skill version-control-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.00025 | $0.00582 |
| Opus 5 | $0.00013 | $0.00291 |
| Sonnet 5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
version-control-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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Control - Activity Skill
Purpose
Enable AI agents to efficiently query history, compute differences, and follow safe workflows across version control systems.
Core Principles
- Always ensure working copy is synchronized before performing operations.
- Prefer read-only operations for history exploration.
- Use explicit time ranges or branch references when querying logs.
- Generate outputs in a consistent, human-readable format.
- Delegate actual command execution to VCS-specific references.
Scenarios
1. Generate Change Logs
Inputs
- Time range:
- today
- yesterday
- last week
Flow
- Resolve the time range into concrete start and end timestamps.
- Query commit history within the range.
- Extract:
- commit identifier
- author
- timestamp
- message
- Format output as chronological log (latest first preferred).
Output Format
Will be as per the version control that you are using.
2. Log Between Two Branches
Assumption
Branches share a common ancestor.
Inputs
- source branch
- target branch
Flow
- Identify commits reachable from one branch and not the other.
- Direction:
- changes in source not in target
- Retrieve commit metadata.
- Present ordered list.
Output Format
Same as change logs.
3. Generate Unified Diff Between Two Branches
Inputs
- base branch
- comparison branch
Flow
- Resolve both branches to their latest revisions.
- Compute differences between trees.
- Generate unified diff format:
- file paths
- additions (+)
- deletions (-)
Output Format
Standard unified diff format
4. Ensure Safe Working State Before Modification
Flow
- Check if local working copy is clean.
- Synchronize with remote repository.
- Handle conflicts if detected.
- Only then allow further operations (outside scope).
Error Handling
- If branches do not share a common ancestor → abort with explanation.
- If working directory is dirty → warn before proceeding.
- If time range yields no commits → return empty result.
What ships with it
3 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.
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.
- yesterday First seen · 116 lines · 25 tokens per session scan A 045a3a7bc264
version-control-skill is a skill published in the GitHub repository nitinbhide/tcaitoolkit (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 582 once invoked, about $0.0001 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…