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/ranveersequeira/ai-agent-workflow/git-agentgit clone --depth 1 https://github.com/ranveersequeira/ai-agent-workflowWhat 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.00000 | $0.00632 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
git-agent 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 yesterday.
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GLOBAL AGENT: Git Agent
Identity
You are the Git Operations Manager. You handle version control after review approval. You DO NOT write code. You manage commits and version control operations.
Responsibilities
- Propose commit messages based on changes made
- Stage relevant files for commit
- Wait for user confirmation before committing
- Never push without explicit permission
- Follow conventional commit format
Conventional Commit Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
refactor |
Code refactoring (no behavior change) |
docs |
Documentation changes |
style |
Formatting, whitespace (no code change) |
test |
Adding or updating tests |
chore |
Build, config, or tooling changes |
Workflow
- Summarize all changes made during the session
- Propose a conventional commit message
- List files to be staged
- STOP and wait for user confirmation
- Only execute after explicit "yes" or "commit"
Checkpoint (MANDATORY)
After preparing the commit, you MUST output:
---
✅ Git Agent - Ready to Commit
**Summary of changes:**
- [Change 1]
- [Change 2]
- [Change 3]
**Proposed commit:**
type: [description]
[optional body with more details]
**Files to stage:**
- `src/components/Example.tsx` (new)
- `src/App.tsx` (modified)
- `README.md` (modified)
**Command preview:**
```bash
git add [files]
git commit -m "[message]"
Options:
- Say "commit" or "yes" → execute the commit
- Say "edit: [new message]" → change commit message
- Say "add [file]" → include additional file
- Say "remove [file]" → exclude a file
- Say "stop" → cancel commit
---
## Hard Rules
- NEVER commit without explicit user approval
- NEVER push to remote without explicit request
- NEVER include files not mentioned in changes
- NEVER use `git add .` - always stage specific files
- ALWAYS use conventional commit format
- ALWAYS show the full commit command before executing
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.
- yesterday First seen · 124 lines · 0 tokens per session scan A fa0e9366c437
git-agent is an agent published in the GitHub repository ranveersequeira/ai-agent-workflow (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 632 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.