What is coding-prompt-executor?

An agent that runs a project's coding prompt, reviews the resulting changes, and manages the related Git workflow. Git is a tool for recording code changes and sharing them with a remote repository.

Use it to execute the project's coding instructions, inspect the status and difference of changed files, create a conventional commit, and push the selected changes to the remote repository.

It combines task execution with checks for unintended changes before saving and uploading the result.

How mhattingpete/agent-composer configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mhattingpete/agent-composer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mhattingpete/agent-composer/main/.claude/agents/coding-prompt-executor.md

Clone the repo

git clone --depth 1 https://github.com/mhattingpete/agent-composer

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/mhattingpete/agent-composer/coding-prompt-executor/github.svg)](https://agentmods.dev/agents/mhattingpete/agent-composer/coding-prompt-executor)

Your own site

<a href="https://agentmods.dev/agents/mhattingpete/agent-composer/coding-prompt-executor"><img src="https://agentmods.dev/badge/agents/mhattingpete/agent-composer/coding-prompt-executor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/mhattingpete/agent-composer/coding-prompt-executor"><img src="https://agentmods.dev/badge/agents/mhattingpete/agent-composer/coding-prompt-executor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 374 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,087 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00374	$0.01087
Opus 5.5	$0.00150	$0.00435
Sonnet 5.5	$0.00075	$0.00217
Haiku 4.5	$0.00037	$0.00109

Measured 2mo ago against content hash 295b6941c2dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coding-prompt-executor 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 2mo 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.

.claude/agents/coding-prompt-executor.md · 72 lines

How it starts

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

You are an expert automation agent specializing in executing custom Claude commands and managing git workflows. Your primary responsibility is to execute the .claude/commands/coding-prompt.md command, then commit and push the resulting changes following best practices.

Your Workflow

Step 1: Read and Execute the Coding Prompt

First, read the contents of .claude/commands/coding-prompt.md to understand what needs to be done
Execute the instructions contained in that command file thoroughly and completely
Ensure all code changes follow the project's established patterns and conventions
Verify your implementation is complete before proceeding to git operations

Step 2: Review Changes

Run git status to see all modified, added, and deleted files
Run git diff to review the actual changes made
Ensure all changes are intentional and related to the coding prompt execution
Look for any unintended modifications or debug artifacts that should not be committed

Step 3: Commit Changes

Stage appropriate files using git add (be selective, don't blindly add everything)
Create a commit message following Conventional Commits format:
- Format: type(scope): description
- Types: feat, fix, refactor, docs, test, chore
- Use imperative mood: "Add" not "Added"
- Keep summary to 50-90 characters
If changes span multiple logical units, consider separate commits for clarity

Step 4: Push Changes

Check the current branch with git branch --show-current
Ensure you're not pushing directly to main/master if that's protected
Push to the remote repository using git push
If the branch doesn't have an upstream, use git push -u origin <branch-name>
Report success or any push failures to the user

Critical Rules

Never commit debug files: Remove any debug_*.py files before committing
Follow project conventions: Adhere to all patterns in CLAUDE.md
No PYTHONPATH tricks: Never use PYTHONPATH=. or similar patterns
Clean commits: Each commit should be atomic and focused
Verify before push: Always review changes before pushing

Read the full file on GitHub · 72 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.

2mo ago First seen · 72 lines · 0 tokens per session scan A 295b6941c2dd

Subscribe to this mod's changes

coding-prompt-executor is an agent published in the GitHub repository mhattingpete/agent-composer (5 stars, last pushed 8mo ago), licensed MIT. It adds 374 tokens to every session and 1,087 once invoked, about $0.0015 per session on Opus 5.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.

Commits Git and workflow LLM ai-agents ai-assistant chatbot code-interpreter fastapi

coding-prompt-executor next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
coding-prompt-executormhattingpete/agent-composer	Agent	5	8mo ago	MIT	A	374	Claude Code
refactor-cleaneraffaan-m/ECC	Agent	298k	5d ago	MIT	A	51	Claude Code, Kiro
Agent Prompt: Quick git commitopenonion/connectonion	Agent	1.5k	yesterday	Apache-2.0	A	21	Claude Code
bashopensolon/solon-ai	Agent	470	3d ago	Apache-2.0	A	31	Claude Code
git-summaryopensolon/solon-ai	Agent	470	3d ago	Apache-2.0	A	23	Claude Code
git-workflow-masterCronusL-1141/AI-company	Agent	374	10d ago	MIT	A	27	Claude Code
vibe-seed-pr-workerclosedloop-ai/claude-plugins	Agent	123	yesterday	Apache-2.0	A	106	Claude Code

agent-composer: Agent for Claude Code