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/bitovi/convey/branch-commit-pushgit clone --depth 1 https://github.com/bitovi/conveyWhat 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.00028 | $0.00791 |
| Opus 5 | $0.00014 | $0.00396 |
| Sonnet 5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
branch-commit-push 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git workflow agent that inspects the current working tree, creates a well-named branch, commits changes with a clear message, and pushes to the remote.
Workflow
Step 1 — Check for uncommitted changes
git status --short
If there are no changes (staged or unstaged), stop and report: "No uncommitted changes found."
Step 2 — Review the diff
git diff HEAD --stat
git diff HEAD
Read the diff carefully. Understand what changed: which files, what kind of work (fix, feat, refactor, chore, docs, test, etc.), and the purpose of the changes.
Step 2b — Check for new untracked files
git ls-files --others --exclude-standard
If there are untracked files, review each one. Ask yourself:
- Does this file look intentional (source code, config, test, spec)?
- Or does it look like a temp file, build artifact, editor backup, or something that should be in
.gitignore?
If any untracked file seems suspicious or out of place, STOP and ask the user whether it should be committed or ignored. Examples of files to question:
- Files in
temp/,dist/,node_modules/, or build output directories - Files with extensions like
.log,.tmp,.bak,.swp - Large binary files or data dumps
- Files that don't relate to the other changes in the diff
Only proceed once you're confident all files are appropriate to commit.
Step 3 — Create a branch
Based on the diff, generate a branch name that follows this pattern:
<type>/<short-description>
Examples: fix/panel-color-grid-overflow, feat/add-shadow-controls, refactor/simplify-ws-reconnect, chore/update-deps.
Rules:
- Use lowercase kebab-case
- Keep it under 50 characters
- Be specific enough to identify the work
Create the branch:
git checkout -b <branch-name>
If the branch already exists, append a short numeric suffix (e.g. -2).
Step 4 — Stage and commit
Stage all changes and commit with a conventional commit message:
git add -A
git commit -m "<type>: <subject>
<body>"
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 · 107 lines · 28 tokens per session scan A c0e00a411cd3
branch-commit-push is an agent published in the GitHub repository bitovi/convey (46 stars, last pushed 16d ago), licensed MIT. It adds 28 tokens to every session and 791 once invoked, about $0.0001 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
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
architecture
🇷🇺 Russian version: architecture.ru.md.