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.
npx agentmods add skills/marcusjellinghaus/mcp-workspace/issue_createnpx skills add MarcusJellinghaus/mcp-workspace --skill issue_creategit 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.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00009 | $0.00393 |
| Opus 5 | $0.00005 | $0.00197 |
| Sonnet 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 5d 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.
- 5d 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 (50 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 393 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.
Other skills, from other repositories
gitnexus-pr-review
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?".
my-complex-skill
Production-ready Model Context Protocol (MCP) server for multi-agent AI consultations (Codex, Claude, Anti-Gravity, Mimo) with Minimax-M3 consensus synthesis.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".