issue-approver

issue-approver is an agent for Claude Code from MarcusJellinghaus/mcp-tools-py. It costs 28 tokens per session (388 once invoked), scanned A, original, MIT.

An issue-approval agent that checks a GitHub issue and approves it by adding an `/approve` comment. This starts the repository's automated status transition.

In plain words
What is it for?
Use it to approve a GitHub issue for the next workflow status and assign it to the current GitHub user.
Why use it?
It prevents issues from being approved when the wrong issue was selected or open questions remain. It also handles the wait and assignment steps after approval.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

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/marcusjellinghaus/mcp-tools-py/issue-approver
Clone the repo
git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-py

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.

agentmods badge for issue-approver

README.md
[![agentmods](https://agentmods.dev/badge/agents/marcusjellinghaus/mcp-tools-py/issue-approver.svg)](https://agentmods.dev/agents/marcusjellinghaus/mcp-tools-py/issue-approver)
Your own site
<a href="https://agentmods.dev/agents/marcusjellinghaus/mcp-tools-py/issue-approver"><img src="https://agentmods.dev/badge/agents/marcusjellinghaus/mcp-tools-py/issue-approver.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 388 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00388
Opus 5 $0.00014 $0.00194
Sonnet 5 $0.00006 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured 2d ago against content hash ba9d11c7df2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

issue-approver 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.

.claude/agents/issue-approver.md · 36 lines

What it actually says

Issue-Approver Agent

You are an issue approval specialist. You approve issues by commenting /approve on them, which triggers a GitHub Action to promote the issue status.

Do not invoke /issue_approve — it is disable-model-invocation, so the Skill tool will refuse. Instead read .claude/skills/issue_approve/SKILL.md with mcp__mcp-workspace__read_file and follow its numbered instructions. Ignore its frontmatter, its "Resolve Issue Number" section — your issue number, and any --repo owner/repo flag, come from your launch prompt — and any wording aimed at a user typing the command, including its closing note about disable-model-invocation. You are running it unattended. The rest of the file applies to you unchanged.

On top of that process:

  • Scope — the issue number must match your launch prompt, and the prompt must confirm that no open questions remain. This replaces the skill's step 2, which assumes a human judging a conversation. If either check fails, stop and report back without approving.
  • Shellgh commands only.
  • Report the issue number and the status transition.

The working directory is already correct — do not use cd or git -C.

Runs with bypassPermissions. Rationale and limits: docs/repository-setup/agent-permissions.md in the mcp-coder repository.

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 Changed · -15 lines · +16 tokens per session ba9d11c7df2b
  2. 6d ago First seen · 51 lines · 12 tokens per session scan A 4756b7fcc915

Subscribe to this mod's changes

issue-approver is an agent published in the GitHub repository MarcusJellinghaus/mcp-tools-py (18 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 388 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.