Borrowing it
Nothing to install: this file belongs to marcmodin/mcp-prompt-server. 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/marcmodin/mcp-prompt-server/main/.claude/commands/create-prompt-issue-request.mdgit clone --depth 1 https://github.com/marcmodin/mcp-prompt-serverWrote 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/commands/marcmodin/mcp-prompt-server/create-prompt-issue-request)<a href="https://agentmods.dev/commands/marcmodin/mcp-prompt-server/create-prompt-issue-request"><img src="https://agentmods.dev/badge/commands/marcmodin/mcp-prompt-server/create-prompt-issue-request.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.1 | $0.00022 | $0.03575 |
| Opus 5 | $0.00011 | $0.01788 |
| Sonnet 5 | $0.00004 | $0.00715 |
| Haiku 4.5 | $0.00002 | $0.00358 |
Grade A, and why
create-prompt-issue-request 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.
How it starts
The opening of the file, as written. The whole thing — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Prompt Request Issue
Context
You are a helpful assistant that guides users through creating a Prompt Request issue on GitHub. You follow the prompt request template defined in .github/ISSUE_TEMPLATE/prompt_request.yml to gather all necessary information about the desired prompt, then create and submit the issue using the GitHub CLI (gh command).
Your goal is to make it easy for users to request new prompts by asking conversational questions based on the template fields.
Instructions
Follow this conversational workflow to create a Prompt Request issue:
1. Introduction
Explain that you'll help create a prompt request issue and gather the necessary information through a series of questions.
2. Read the Template
Read the prompt request template at .github/ISSUE_TEMPLATE/prompt_request.yml to understand all required and optional fields.
3. Gather Information in Chunks
Ask the user questions in three groups to make the process faster and more efficient. Use the XML structure below to organize the data collection:
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.
- 7d ago First seen · 413 lines · 22 tokens per session scan A 8d92e8e99624
create-prompt-issue-request is a command published in the GitHub repository marcmodin/mcp-prompt-server (1 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 3,575 once invoked, about $0.0001 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-31.
Other commands, from other repositories
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
backlot
Open the Backlot living storyboard — the browser board that shows pipeline stages, script, scene plan, and generated assets live as a production runs.
arrange-workspace-flow-choose-workspace-layout
Phase 1 Choose Workspace Layout of arrange-workspace-flow.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.