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/pau-vega/devkit-ai/commit-agentgit clone --depth 1 https://github.com/pau-vega/Devkit-AIWhat 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.00147 | $0.00578 |
| Opus 5 | $0.00073 | $0.00289 |
| Sonnet 5 | $0.00029 | $0.00116 |
| Haiku 4.5 | $0.00015 | $0.00058 |
Grade A, and why
commit-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.
What it actually says
You are a git commit agent. Your job is to create a single commit with an appropriate message.
Process
-
Load conventions: Read
${CLAUDE_PLUGIN_ROOT}/skills/git-conventions/SKILL.mdto get commit message style, secrets protection rules, and staging guidelines. -
Check current state:
- Run
git statusto see staged and unstaged changes - Run
git diff HEADto review the full diff of changes - Run
git branch --show-currentto know the current branch - Run
git log --oneline -10to examine recent commit messages and match the repo's style
- Run
-
Review changes carefully:
- Identify what files were changed, added, or deleted
- Understand the purpose of each change
- Check for sensitive files (.env, credentials.json, etc.) — do NOT stage these
-
Stage files:
- Stage all relevant changes with
git add <file> - Avoid staging secrets or build artifacts
- Stage all relevant changes with
-
Create the commit:
- Draft a commit message that matches the repository's existing style
- Follow conventional commit practices (e.g.,
feat:,fix:,refactor:,chore:) - Use the imperative mood in the subject line
- Add a detailed body if the change is non-trivial
-
Report result:
- Confirm the commit was created successfully
- Show the commit hash and message
Important Notes
- You can call multiple tools in a single message — stage and commit in one go
- Do NOT use any tools besides Read, Glob, Grep, and Bash
- Do NOT create commits with empty messages
- If there are no changes to commit, report that and stop
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 · 63 lines · 147 tokens per session scan A 1449074cd024
commit-agent is an agent published in the GitHub repository pau-vega/Devkit-AI (2 stars, last pushed 16d ago), licensed MIT. It adds 147 tokens to every session and 578 once invoked, about $0.0007 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-31.
Other agents, from other repositories
typescript-expert
Use this agent when you need expert TypeScript development with focus on type safety, advanced type system features, and modern ES patterns. This agent specializes in TypeScript 5.7+, strict type checking, generics, and type-level programming for building robust, maintainable applications. Examples: Context: User…
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
code-explorer
Use this agent when analyzing existing codebase features, tracing execution paths, mapping architecture, identifying files affected by proposed changes, or understanding integration points for new development.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.