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_create/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_create)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/issue_create"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/issue_create/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_create"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/issue_create.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.00009 | $0.00393 |
| Opus 5.5 | $0.00004 | $0.00157 |
| Sonnet 5.5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
issue_create 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
Create GitHub Issue
Based on our prior discussion, create a GitHub issue.
Instructions:
- Extract the issue title and body from the conversation context
- Use a clear, descriptive title
- Include relevant details from our discussion in the body
- Use markdown formatting for better readability
Link related issues. If the issue belongs to an epic or design doc, or has dependencies, list them near the top and in a ## Dependencies / references section — the epic, design doc, dependencies, and any curated sibling issues worth reading. Add a short "read these first" note when they're essential. Omit for standalone issues.
Optional: Base Branch If the feature should be based on a branch other than the default (main/master), include:
### Base Branch
<branch-name>
Use cases:
- Hotfixes based on release branches
- Features building on existing work
- Long-running feature branches
Important: Before specifying a base branch, verify it exists:
Call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", "origin", "<branch-name>"].
If no base branch is needed, omit this section entirely.
Create the issue using:
mcp__mcp-workspace__github_issue_create(title="TITLE", body="BODY")
The body is passed inline — no escaping, no heredoc, no temp file.
If no prior discussion context is found, respond: "No discussion context found. Please discuss the feature or bug first before creating an issue."
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 · 49 lines · 9 tokens per session scan A 8e36bd7b1b33
issue_create is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (48 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 393 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.