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 memovai/memov --skill vibegitgit clone --depth 1 https://github.com/memovai/memovWrote 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/memovai/memov/vibegit)<a href="https://agentmods.dev/skills/memovai/memov/vibegit"><img src="https://agentmods.dev/badge/skills/memovai/memov/vibegit/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/memovai/memov/vibegit"><img src="https://agentmods.dev/badge/skills/memovai/memov/vibegit.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.01260 |
| Opus 5.5 | $0.00000 | $0.00504 |
| Sonnet 5.5 | $0.00000 | $0.00252 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade C, and why
vibegit scanned grade C with 2 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 2mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/memovai/memov/main/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/memovai/memov/main/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeGit - AI Coding History
AI-assisted version control using Memov. Track every AI interaction with your codebase.
Prerequisites
This skill requires the memov Python package which provides the mem CLI command.
Installation Options
Choose one of the following methods:
# Option 1: Official install script (recommended)
curl -fsSL https://raw.githubusercontent.com/memovai/memov/main/install.sh | bash
Verify Installation
mem
Initialize in Your Project
cd your-project
mem init
How to Use
There are two ways to use VibeGit:
- Skill scripts (this folder): run
./scripts/*.shto call the localmemCLI. - MCP tools (Claude Code): use the MCP server tools like
mcp__mem-mcp__snap.
They are related but not identical:
- Skill scripts are a thin wrapper over
memCLI. - MCP tools may add extra behavior (e.g. auto-track untracked files, auto-sync for RAG features).
Commands
All commands should be run from the skill directory using the scripts provided.
Core Operations
| Script | Description | Usage |
|---|---|---|
init.sh |
Initialize memov in a project | ./scripts/init.sh |
track.sh |
Track new files | ./scripts/track.sh file1.py file2.py -p "..." -r "..." |
snap.sh |
Record a code change | ./scripts/snap.sh --files "file1.py,file2.py" -p "What was asked" -r "What was done" |
history.sh |
View AI coding history | ./scripts/history.sh [--limit 20] |
show.sh |
Show commit details | ./scripts/show.sh <commit_hash> |
status.sh |
Check working directory status | ./scripts/status.sh |
Navigation
| Script | Description | Usage |
|---|---|---|
jump.sh |
Jump to a specific snapshot | ./scripts/jump.sh <commit_hash> |
branch.sh |
List/create/delete branches | ./scripts/branch.sh [name] [--delete name] |
switch.sh |
Switch branches | ./scripts/switch.sh <branch_name> |
Web UI
Before running mem ui start, confirm where you want to open the UI:
What ships with it
15 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.
- .claude-plugin/plugin.json 577 B
- install.sh 377 B runs code
- scripts/_check_deps.sh 542 B runs code
- scripts/branch.sh 164 B runs code
- scripts/history.sh 146 B runs code
- scripts/init.sh 171 B runs code
- scripts/jump.sh 224 B runs code
- scripts/show.sh 230 B runs code
- scripts/snap.sh 1.6 KB runs code
- scripts/status.sh 138 B runs code
- scripts/switch.sh 221 B runs code
- scripts/track.sh 186 B runs code
- scripts/ui_start.sh 333 B runs code
- scripts/ui_status.sh 322 B runs code
- scripts/ui_stop.sh 360 B runs code
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.
- 2mo ago First seen · 188 lines · 0 tokens per session scan C a301a487838f
vibegit is a skill published in the GitHub repository memovai/memov (194 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,260 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
kirocrew-worktree-dev
HARD RULE for developing the Kiro Crew source repo ITSELF (not users' projects): develop, build and verify in a git worktree, never against the live gateway. Covers env setup, main-clone sync, build/dist ordering, flags, previews, cleanup, publish authorization; kirocrew-prepare-pr owns PRs.
bmad-walkthrough
Guide a human review of a commit, PR, file, or directory. Use when invoked by name.
vigilante-issue-implementation
Implement a GitHub issue end-to-end when Vigilante dispatches work for a watched repository. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.