agentmods.dev

mcp-workspace: Skill for Claude Code

.claude/skills/issue_approve/SKILL.md

issue_approve is a skill for Claude Code from MarcusJellinghaus/mcp-workspace. It costs 8 tokens per session (915 once invoked), scanned A, original, MIT.

A workflow command that approves an issue so it can move to the next status. An issue is a tracked piece of work or problem in a project.

In plain words
What is it for?
Use it to approve a known issue, determine its issue number from project context, and transition it through the configured workflow.
Why use it?
It avoids manually navigating the issue system and checks which issue and repository should be updated.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is MarcusJellinghaus/mcp-workspace's own configuration. It tells Claude Code how to work on mcp-workspace itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-workspace configures →

not rated 50repo changed 7d ago A scan SkillSpector: pass 8 tokens original MIT
View source ↗ MarcusJellinghaus/mcp-workspace
Reuse

Borrowing it

Nothing to install: this file belongs to MarcusJellinghaus/mcp-workspace. 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/MarcusJellinghaus/mcp-workspace/main/.claude/skills/issue_approve/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspace

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_approve

README.md
[![agentmods](https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/issue_approve/github.svg)](https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/issue_approve)
Your own site
<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/issue_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/issue_approve/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.

agentmods 80×15 button for issue_approve

Your own site · 80×15
<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/issue_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/issue_approve.svg" alt="Reviewed on agentmods" width="80" 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 915 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00008 $0.00915
Opus 5 $0.00004 $0.00458
Sonnet 5 $0.00002 $0.00183
Haiku 4.5 $0.00001 $0.00092

Measured 7d ago against content hash 791e804a033c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 7d 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/skills/issue_approve/SKILL.md · 87 lines

How it starts

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

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, first check whether that repo is a configured reference project — match owner/repo against the url of each entry get_reference_projects() returns. If it is, use the MCP tools with that entry's name as reference_name: mcp__mcp-workspace__github_issue_view and mcp__mcp-workspace__github_issue_comment both reach it. Only when the repo is not a configured reference project, fall back to the gh commands below, appending --repo owner/repo to each.

Instructions

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

    Note its current status label — step 5 compares against it.

  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:

mcp__mcp-workspace__github_issue_comment(number=<issue_number>, body="/approve")

For a cross-repo issue (--repo owner/repo) that is a configured reference project, pass its reference_name:

mcp__mcp-workspace__github_issue_comment(number=<issue_number>, body="/approve", reference_name=<name>)

For any other repo, use Bash instead — the MCP tool only reaches the workspace repository and its configured reference projects. MSYS_NO_PATHCONV=1 prevents Windows Git Bash from rewriting the leading / and is needed only for this Bash form:

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

  1. 7d ago Changed · +10 lines 791e804a033c
  2. 9d ago First seen · 77 lines · 8 tokens per session scan A 12ae6b4a49d2

Subscribe to this mod's changes

issue_approve is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (50 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 915 once invoked, about $0.0000 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.

Project managementclaude-desktopfile-operationsfilesystemmcpmcp-servermodel-context-protocol
Related

Other skills, from other repositories

report-issue

File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.

cyanheads/git-mcp-server · 51 tokens

bulk-update

Update properties or content across many pages in a Notion database with dry-run and error recovery.

n24q02m/better-notion-mcp · 21 tokens

quick-capture

Use this skill to drop a new task into GSD Task Manager from any AI assistant that has the gsd-mcp-server connected.

vscarpenter/gsd-task-manager · 0 tokens

onplana-project-planner

Turn a goal or a brief into an executable Onplana plan over its MCP server: write a plan.md and attach it to the project, decompose it into tasks and subtasks, set start/due dates and dependencies, assign owners, add test cases as you go, and create tasks for the downstream surfaces a change ripples to. Use this…

Onplana/onplana-mcp-server · 133 tokens

event-staffing-ordering

Order W-2 event staff for US/CA events through TempGuru.

Tempguru-co/tempguru-mcp · 22 tokens

onplana-autonomous-agent

Work autonomously on projects in Onplana over its MCP server: pick up the open tasks in a project, do the work, keep each task's status current, report progress as comments, file an Issue when something is wrong, and poll for human replies. Use this whenever an agent (Claude Code, ChatGPT / Codex, or claude.ai) is…

Onplana/onplana-mcp-server · 102 tokens