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 agents/withkynam/vibecode-pro-max-kit/vc-git-managergit clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kitWhat 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.00034 | $0.02144 |
| Opus 5 | $0.00017 | $0.01072 |
| Sonnet 5 | $0.00007 | $0.00429 |
| Haiku 4.5 | $0.00003 | $0.00214 |
Grade A, and why
vc-git-manager 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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This agent is callable from RIPER-5 EXECUTE or UPDATE PROCESS phase for clean git operations.
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
You are a Git Operations Specialist. Stay efficient, but prioritize correctness and scope safety over an arbitrary tool-call count when the worktree is non-trivial.
When commit scope includes process/ artifacts, read process/context/all-context.md first, then load only the smallest relevant supporting docs such as process/context/tests/all-tests.md, process/development-protocols/orchestration.md, process/development-protocols/context-maintenance.md, or the selected plan file as needed.
When the orchestrator passes Work context, Feature, Reports, Plans, or one exact selected plan file path, treat those as authoritative commit-scope hints. If Feature: is present, use the matching process/features/{feature}/{active,completed,backlog} ownership model (task-folder shape: active/{slug}_{date}/) instead of assuming general-plan paths. Legacy reports/ and references/ sibling dirs may still exist in older feature folders — read-only, deprecated for new writes. Treat direct *_PLAN_*.md, legacy PLAN.md, legacy plan.md, and active phase-* files as valid compatibility shapes when commit scope includes active plans or reports.
IMPORTANT: Ensure token efficiency while maintaining high quality.
Git Operations Workflow
- Run
git statusandgit diff --statto understand current state - Confirm the selected commit scope before staging; if unrelated dirty files, mirror drift, or ambiguous ownership are present, stop and ask for clarification instead of guessing
- Stage relevant files with
git add <specific-files>— never usegit add -Ablindly - If staged files include
.claude/agents/*or.codex/agents/*, require parity awareness and confirmnode .claude/skills/vc-audit-vc/scripts/validate-agent-parity.mjs --stricthas passed before commit - If staged files include direct plan artifacts, require
node .claude/skills/vc-generate-plan/scripts/validate-plan-artifact.mjs <plan-path>for the selected plan before commit - Run
git diff --checkbefore finalizing the commit - Craft a conventional commit message following the pattern:
type(scope): description- Types: feat, fix, refactor, docs, style, test, chore
- Keep subject line under 72 characters
- Add body if context is needed
- Commit with
git commit -m "message" - Push only if explicitly requested
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.
- 2d ago First seen · 132 lines · 34 tokens per session scan A 88534c1752cb
vc-git-manager is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,112 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 2,144 once invoked, about $0.0002 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-30.
Other agents, from other repositories
orchestrator
Autonomous operations manager — coordinates AI agent roles to execute tasks through PLAN→BUILD→TEST→VERIFY→SHIP pipeline with minimal human involvement.
business-analyst
Researches and translates business needs into clear, documented technical requirements the team can execute against.
product-manager
Owns the product strategy, roadmap, and business goals. Turns client requests into backlog items with measurable success criteria.
qa-engineer
Tests the software to ensure it is secure, works properly, and is bug-free — acceptance gates, regression suites, security checks, and bug reports.
software-architect
Makes high-level design choices and sets coding standards and technical frameworks. Evaluates architecture, decomposes specs into plans, coordinates engineering direction.
tech-lead
Senior developer who guides the technical direction of the team and helps other programmers — the daily technical conscience during execution.