agentmods.dev

issue_approve

issue_approve is a skill for Claude Code, Codex from MarcusJellinghaus/mcp-tools-sql. It costs 8 tokens per session (519 once invoked), scanned A, a copy of issue_approve, MIT.

An issue-workflow skill for approving a GitHub issue so it can move to its next status.

In plain words
What is it for?
Use it to check the issue, confirm that requirements are clear and no blocking questions remain, and add the approval comment.
Why use it?
It prevents issues from advancing before they have been reviewed, discussed, and made clear enough to act on.

Skill for Claude CodeCodex

not rated 2 6d ago A scan 8 tokens copy · 94% MIT
View the source file MarcusJellinghaus/mcp-tools-sql
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 skills/marcusjellinghaus/mcp-tools-sql/issue_approve
Any agent
npx skills add MarcusJellinghaus/mcp-tools-sql --skill issue_approve
Clone the repo
git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sql

Made for: Claude Code, Codex.

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_approve

README.md
[![agentmods](https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/issue_approve.svg)](https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/issue_approve)
Your own site
<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/issue_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/issue_approve.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 519 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% 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.00008 $0.00519
Opus 5 $0.00004 $0.00260
Sonnet 5 $0.00002 $0.00104
Haiku 4.5 $0.00001 $0.00052

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

Security

Grade A, and why

issue_approve 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 4d 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

94% identical to issue_approve — 16 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.

.claude/skills/issue_approve/SKILL.md · 53 lines

What it actually says

Approve Issue

Approve the current issue to transition it to the next status in the workflow.

Resolve Issue Number

The user may provide an issue number as the argument (available as $ARGUMENTS). If no issue number is provided:

  1. Check if the issue number is known from prior /issue_analyse or /issue_create in this conversation
  2. Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
  3. If still unknown, ask the user

Cross-Repo Issues

If a --repo owner/repo flag was given, append it to every gh command below, and fetch the issue with gh issue view <issue_number> --repo owner/repo via Bash — mcp__mcp-workspace__github_issue_view only reaches the current repository.

Instructions

  1. Fetch the issue to confirm it exists: Call mcp__mcp-workspace__github_issue_view with the issue number (or gh issue view for cross-repo).

  2. Validate that the issue is ready for approval:

    • Issue has been analyzed/discussed
    • Requirements are clear
    • No blocking questions remain

    If any check fails, stop and report — do not approve.

  3. Comment /approve on the issue (use MSYS_NO_PATHCONV to prevent Windows Git Bash path conversion):

MSYS_NO_PATHCONV=1 gh issue comment <issue_number> --body "/approve"

This triggers the GitHub Action to promote the issue status (e.g., status-01:created → status-02:awaiting-planning).

  1. Report the issue number and the approval result.

Note: This skill has disable-model-invocation — it can only be run by the user typing /issue_approve. If you need this skill as a follow-up, tell the user: "Please run /issue_approve to proceed."

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. 4d ago First seen · 53 lines · 8 tokens per session scan A 70a14843a5c3

Subscribe to this mod's changes

issue_approve is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 519 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to issue_approve, differing in 16 lines, and is treated as a copy.

Project management
Related

Other skills, from other repositories

wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

mattpocock/skills · 46 tokens

timeline-creator

Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.

mhattingpete/claude-skills-marketplace · 47 tokens

pm-all

Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).

wei63w/pm-manager · 8 tokens

bootstrap-prd

Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.

joshukraine/dotfiles · 25 tokens

simulator-reactions

Simulator.Company reactions specialist — comments, events, approvals, ratings and other feedback attached under an actor. Use when the user wants to comment on an actor, reply in a thread, read/like/pin the discussion, mark comments read, or get reaction stats. Activate when the user says "comment on this actor"…

corezoid/simulator-ai-plugin · 174 tokens

glab-issue

Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…

vince-winkintel/gitlab-cli-skills · 89 tokens