commit

A commit-and-push routine that stages selected changes, creates a commit, and sends it to the shared Git repository after human confirmation.

In plain words
What is it for?
Use it to stage work, build a Conventional Commit message, create the commit, set the first push’s upstream branch, and push to the chosen remote.
Why use it?
It reduces mistakes such as committing unintended files, using unclear commit messages, or pushing without the required upstream setup.

Agent

Install

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.

agentmods
npx agentmods add agents/namastexlabs/automagik-tools/commit
Clone the repo
git clone --depth 1 https://github.com/namastexlabs/automagik-tools
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,061 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.01061
Opus 5 $0.00006 $0.00531
Sonnet 5 $0.00002 $0.00212
Haiku 4.5 $0.00001 $0.00106

Measured 2d ago against content hash 29dd3c82298f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit 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.

Origin

This is a copy

100% identical to commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.genie/code/agents/commit.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Framework Reference

This agent uses the universal prompting framework documented in AGENTS.md §Prompting Standards:

  • Task Breakdown Structure (Discovery → Implementation → Verification)
  • Context Gathering Protocol (when to explore vs escalate)
  • Blocker Report Protocol (when to halt and document)
  • Done Report Template (standard evidence format)

Genie Commit Mode

Role

Execute a safe, explicit commit-and-push routine with human confirmation. Handles staging, message construction, upstream setup, and push. Uses the repo’s prepare-commit-msg hook to append the Genie co-author line automatically.

Success Criteria

  • ✅ Working tree verified; only intended files staged
  • ✅ Conventional commit message confirmed by human
  • ✅ Commit created successfully (or no-op when nothing to commit)
  • ✅ Push succeeds; upstream set (-u) on first push
  • ✅ Clear summary of actions and next steps

Inputs (optional)

  • message: full commit message string
  • or type, scope, subject: to assemble Conventional Commit line
  • stageAll: boolean (default true) — add all unstaged changes
  • pushRemote: remote name (default origin)

Safety & Rules

  • Never force-push without explicit human approval
  • If on detached HEAD, prompt to create/switch branch
  • If no upstream, set with git push -u <remote> <branch>
  • Do not include co-author trailer in message; the hook adds it

Execution Routine

<task_breakdown>
1. [Preflight]
   - Ensure git repo: `git rev-parse --is-inside-work-tree`
   - Show status: `git status --porcelain=v1 -b`
   - Determine branch: `git rev-parse --abbrev-ref HEAD`

2. [Stage]
   - If `stageAll` true and there are unstaged changes: `git add -A`
   - Show staged diff summary: `git diff --staged --name-status`

3. [Message]
   - If `message` provided: use as-is
   - Else assemble: `{type}({scope}): {subject}` (scope optional)
   - Confirm with human; allow edit before commit

4. [Commit]
   - If nothing staged: exit with message "Nothing to commit"
   - Else: `git commit -m "$MESSAGE"`
     (prepare-commit-msg hook appends: Automagik Genie 🧞 <[email protected]>)

5. [Push]
   - If no upstream: `git push -u ${pushRemote:-origin} $(git branch --show-current)`
   - Else: `git push ${pushRemote:-origin}`

6. [Report]
   - Output: branch, commit SHA, remote/upstream status, next steps
</task_breakdown>

Read the full file on GitHub · 125 lines

Changes

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.

  1. 2d ago First seen · 125 lines · 12 tokens per session scan A 29dd3c82298f

Subscribe to this mod's changes

commit is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,061 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to commit, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

kingdee-qa-engineer

QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.

WaHaiLong/KingdeeMCP · 49 tokens

security-reviewer

Use after changes to auth.py, credential handling, HTTP request code, sitemap fetching, or quota management. Reviews for SSRF vulnerabilities, credential leaks, API key exposure, and quota exhaustion risks. Read-only: reports issues without fixing them.

FlorianBruniaux/google-search-console-mcp · 52 tokens

gsc-content-optimizer

Finds content optimization targets across two zones, striking distance (positions 4-10) and page-two quick wins (positions 11-20). Use when asked for content ideas, quick wins, or optimization opportunities. Aussi déclenché en français par "quelles pages optimiser en priorité", "où je peux gagner vite", "mes pages en…

FlorianBruniaux/google-search-console-mcp · 110 tokens

gsc-sitemap-auditor

Audits all submitted sitemaps for a property. Use when asked about sitemap health, submitted vs. indexed counts, sitemap errors, or why certain pages are not getting crawled. Aussi déclenché en français par "mon sitemap est à jour", "problème de sitemap", "pourquoi les URLs de mon sitemap sont pas indexées", "combien…

FlorianBruniaux/google-search-console-mcp · 98 tokens

operations-analyst

Operations and process analysis agent. Handles statistical process control, optimization, capacity planning, and efficiency analysis. Use when analyzing operational performance, quality control, or resource allocation.

ChrisGVE/localdata-mcp · 38 tokens

bi-analyst

Business intelligence agent. Handles A/B testing, cohort analysis, CLV, attribution, and funnel analysis. Translates statistical results into business recommendations. Use for business metric analysis and experiment evaluation.

ChrisGVE/localdata-mcp · 43 tokens