agentmods.dev

source-control

A set of Git tools for checking a project's version-control state, reviewing changes, viewing history, and saving selected files as commits. Git is software that records changes to code over time.

In plain words
What is it for?
Use it to inspect branches and changed files, review diffs, read commit history, and create focused commits with clear messages.
Why use it?
It helps an agent save work without accidentally committing secrets, environment files, or unrelated large assets. It also makes changes reviewable before they are saved.

Skill for Claude CodeCodex

15 23d ago A scan 0 tokens original MIT
View the source file ezesubu/VERA
Install

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.

agentmods
npx agentmods add skills/ezesubu/vera/source-control
Any agent
npx skills add ezesubu/VERA --skill source-control
Clone the repo
git clone --depth 1 https://github.com/ezesubu/VERA

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 411 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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 $0.00000 $0.00411
Opus 5 $0.00000 $0.00205
Sonnet 5 $0.00000 $0.00082
Haiku 4.5 $0.00000 $0.00041

Measured 3d ago against content hash 97ea89de5e87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

source-control 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 3d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (_git.py, tools/git_commit.py, tools/git_diff.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

UE57/VERA_Plugins/source-control/SKILL.md · 31 lines

What it actually says

Source control (git)

VERA can use source control to save its own work. Four git tools are available: git_status, git_diff, git_log, and git_commit. They operate directly on the project's git repository via the git command line.

How to use them

  1. Always check git_status first. Before committing anything, look at the branch you are on and the exact list of changed/untracked files. Never commit blind.
  2. Review with git_diff when you want to confirm what actually changed in a file (pass path to focus on one file, staged=true to see what is staged).
  3. Commit with EXPLICIT paths only. git_commit requires a paths list and stages only those paths. There is no "add all" -- this repo contains large game assets (.uasset, .umap) and an .env file with secrets that must never be committed. Name every file you intend to commit.
    • .env-style paths are hard-refused.
    • .uasset / .umap are allowed but warned about; avoid committing them unless explicitly asked.
  4. Write clear conventional-commit messages (e.g. feat: ..., fix: ..., docs: ...), matching the style you see in git_log.
  5. Prefer a feature/* branch. The user's current working branch is feature/ui-redesign; keep VERA's commits on a feature branch, not on main.

Safety

git_commit is destructive (it writes history) and is gated -- it asks the user for confirmation before running. The read-only tools (git_status, git_diff, git_log) run without confirmation.

Files

What ships with it

6 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.

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. 3d ago First seen · 31 lines · 0 tokens per session scan A 97ea89de5e87

Subscribe to this mod's changes

source-control is a skill published in the GitHub repository ezesubu/VERA (15 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 411 tokens. 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.

Git and workflowLLMai-agentcopilotmcpunreal-engine
Related

Other skills, from other repositories

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

skill-intake

Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted.

nyldn/claude-octopus · 34 tokens

bf-to-agents-sdk-dotnet-migration

Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.

microsoft/Agents · 56 tokens

build-and-run-macos-app

Slash command that creates or updates the project-local macOS script/buildandrun.sh and uses it as the default build/run entrypoint. Invoke explicitly with /build-and-run-macos-app — this skill never self-triggers.

robinebers/openusage · 54 tokens

macos-packaging-notarization

Prepare macOS packaging and notarization workflows. Use when archiving apps, validating bundles, or explaining distribution-only failures.

robinebers/openusage · 32 tokens

macos-swiftpm

Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.

robinebers/openusage · 35 tokens