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 ezesubu/VERA --skill source-controlgit clone --depth 1 https://github.com/ezesubu/VERAWrote 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/ezesubu/vera/source-control)<a href="https://agentmods.dev/skills/ezesubu/vera/source-control"><img src="https://agentmods.dev/badge/skills/ezesubu/vera/source-control/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/ezesubu/vera/source-control"><img src="https://agentmods.dev/badge/skills/ezesubu/vera/source-control.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.00000 | $0.00411 |
| Opus 5.5 | $0.00000 | $0.00164 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
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 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.
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
- Always check
git_statusfirst. Before committing anything, look at the branch you are on and the exact list of changed/untracked files. Never commit blind. - Review with
git_diffwhen you want to confirm what actually changed in a file (passpathto focus on one file,staged=trueto see what is staged). - Commit with EXPLICIT paths only.
git_commitrequires apathslist and stages only those paths. There is no "add all" -- this repo contains large game assets (.uasset,.umap) and an.envfile with secrets that must never be committed. Name every file you intend to commit..env-style paths are hard-refused..uasset/.umapare allowed but warned about; avoid committing them unless explicitly asked.
- Write clear conventional-commit messages (e.g.
feat: ...,fix: ...,docs: ...), matching the style you see ingit_log. - Prefer a
feature/*branch. The user's current working branch isfeature/ui-redesign; keep VERA's commits on a feature branch, not onmain.
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.
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.
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 First seen · 31 lines · 0 tokens per session scan A 97ea89de5e87
source-control is a skill published in the GitHub repository ezesubu/VERA (21 stars, last pushed 2mo 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.
Other skills, from other repositories
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
release-debrief
Summarises the delta between a tool's latest release and the last summary the user saw. Use when the user asks about what's new, the latest release, release notes, or the changelog of one of the supported tools: Claude Code, OpenCode, llama-swap, or llama.cpp.
github
You MUST always activate this github skill whenever working with GitHub in any capacity, including but not limited to gh cli, API, Actions, issues, PRs and other routine Github interactions.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.