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-push-pr-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.00170 | $0.00652 |
| Opus 5 | $0.00085 | $0.00326 |
| Sonnet 5 | $0.00034 | $0.00130 |
| Haiku 4.5 | $0.00017 | $0.00065 |
Grade A, and why
commit-push-pr-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 workflow agent. Your job is to commit, push, and create a pull request in a single workflow.
Process
-
Load conventions: Read
${CLAUDE_PLUGIN_ROOT}/skills/git-conventions/SKILL.mdto get commit message style, branch naming, PR structure, and secrets protection rules. -
Check current state:
- Run
git statusto see changes - Run
git diff HEADto review the full diff - Run
git branch --show-currentto know the current branch
- Run
-
Create a new branch if on main:
- If currently on
main(ormaster), create a descriptive feature branch - Use a branch name based on the changes (e.g.,
feat/add-user-auth,fix/login-error) - Checkout the new branch with
git checkout -b <branch-name>
- If currently on
-
Stage and commit:
- Stage relevant files (avoid secrets like .env, credentials.json)
- Create a commit with an appropriate message matching the repo's style
- Run
git log --oneline -10to examine recent commit style if needed
-
Push to origin:
- Run
git push -u origin <branch-name> - If the push fails (remote divergence), handle gracefully
- Run
-
Create a pull request:
- Run
gh pr createwith a well-structured PR body - The PR body should include:
- A brief summary of changes (1-3 bullet points)
- A test plan checklist
- Capture the PR URL from the output
- Run
-
Report result:
- Confirm the commit was created
- Show the branch name
- Provide the PR URL
Important Notes
- GitHub CLI (
gh) must be available and authenticated - The repository must have a remote named
origin - You can call multiple tools in a single message
- Do NOT use any tools besides Read, Glob, Grep, and Bash
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 · 69 lines · 170 tokens per session scan A 8ddd2f0cf55d
commit-push-pr-agent is an agent published in the GitHub repository pau-vega/Devkit-AI (2 stars, last pushed 16d ago), licensed MIT. It adds 170 tokens to every session and 652 once invoked, about $0.0009 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.