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.
curl -O https://raw.githubusercontent.com/MarcusJellinghaus/mcp-workspace/main/.claude/skills/issue_update/SKILL.mdgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspaceWrote 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.
[](https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/issue_update)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/issue_update"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/issue_update/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.
<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/issue_update"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/issue_update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.00461 |
| Opus 5.5 | $0.00004 | $0.00184 |
| Sonnet 5.5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
issue_update 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 1mo 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.
What it actually says
Update GitHub Issue
Based on our prior /issue_analyse discussion, update the GitHub issue with refined content.
Instructions:
-
If no issue context is found from prior analysis, respond: "No issue context found. Please run
/issue_analyse <number>first." -
First, fetch the current issue content: Call
mcp__mcp-workspace__github_issue_viewwith the issue number. -
Draft updated issue text with:
- Clear, concise title
- Well-structured body with implementation ideas
-
Update the issue in one call:
mcp__mcp-workspace__github_issue_edit(number=<issue_number>, title="NEW_TITLE", body=body_content)
The body is passed inline — no temp file, no bash escaping.
Editing Base Branch:
- To add a base branch: Insert
### Base Branchsection with the branch name - To change a base branch: Update the content under the existing section
- To remove a base branch: Delete the entire
### Base Branchsection
The base branch must be a single line. Multiple lines will cause an error during branch creation.
The updated issue should include:
- Summary of the requirement
- Discussed implementation approach (concise)
## Constraints & Rationale— non-obvious gotchas and the "why" behind decisions. Skip if none identified.## Decisionstable — decided topics so/issue_analysewon't re-ask. Skip if none yet.## Dependencies / references— preserve the links to the epic, design doc, dependencies, and curated siblings when rewriting; add the section if missing and the issue isn't standalone.
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.
- 1mo ago First seen · 47 lines · 10 tokens per session scan A 5d579a13048f
issue_update is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (48 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 461 once invoked, about $0.0000 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-30.
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.
build-flow
Create or change a Keboola flow that runs extractors, transformations and writers in order, optionally on a schedule. Use when the user wants to orchestrate, chain or schedule existing Keboola configurations.
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
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.
papi-plan
Invoke when starting a new PAPI cycle. Covers plan generation, board management, and cycle scoping rules.
papi-idea
Invoke when submitting backlog ideas, registering docs, or filing research. Covers idea pipeline and doc registry conventions.