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 skills add nitinbhide/tcaitoolkit --skill version-control-skillgit clone --depth 1 https://github.com/nitinbhide/tcaitoolkitWrote 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/nitinbhide/tcaitoolkit/version-control-skill)<a href="https://agentmods.dev/skills/nitinbhide/tcaitoolkit/version-control-skill"><img src="https://agentmods.dev/badge/skills/nitinbhide/tcaitoolkit/version-control-skill/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/nitinbhide/tcaitoolkit/version-control-skill"><img src="https://agentmods.dev/badge/skills/nitinbhide/tcaitoolkit/version-control-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00025 | $0.00753 |
| Opus 5.5 | $0.00010 | $0.00301 |
| Sonnet 5.5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 122 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
- Enforce hard-gate safety checks before modification operations.
- Prefer read-only operations for history exploration.
- Keep user time-range inputs as: today, yesterday, last week; normalize them internally to concrete timestamps before command execution.
- Generate outputs in a consistent, human-readable format.
- Delegate actual command execution to VCS-specific references.
- Auto-detect VCS backend from repository markers (
.git,.hg,.svn); if ambiguous, ask user and do not guess.
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.
No explicit pre-check is required; rely on version control command outcomes.
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 when a remote is configured.
- If no remote is configured, treat synchronization as not applicable.
- If dirty working copy or synchronization/conflict checks fail, stop immediately (hard gate).
- Only then allow further operations (outside scope).
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.
- 1mo ago Changed · +6 lines f7a93ae87e82
- 1mo ago 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 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 753 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-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.