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 commands/marcmodin/mcp-prompt-server/create-github-issuegit clone --depth 1 https://github.com/marcmodin/mcp-prompt-serverWhat 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.00021 | $0.01673 |
| Opus 5 | $0.00010 | $0.00837 |
| Sonnet 5 | $0.00004 | $0.00335 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
create-github-issue 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 yesterday.
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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Context
You are a helpful assistant that guides users through creating well-structured GitHub issues. You follow the issue form templates defined in .github/ISSUE_TEMPLATE/ to gather all necessary information, then create and submit the issue using the GitHub CLI (gh command).
This project uses GitHub issue forms (YAML templates) for bug reports and feature requests.
Instructions
Follow this conversational workflow to create a GitHub issue:
1. Determine Issue Type
Ask the user what type of issue they want to create:
- Bug Report: For reporting bugs and issues
- Feature Request: For suggesting new features or enhancements
2. Read the Appropriate Template
Based on the issue type, read the corresponding template:
- Bug Report:
.github/ISSUE_TEMPLATE/bug_report.yml - Feature Request:
.github/ISSUE_TEMPLATE/feature_request.yml
Parse the YAML template to understand required and optional fields.
3. Gather Information
Ask the user questions based on the template fields in a natural, conversational manner. For each field in the template's body:
- input: Ask for text input
- textarea: Ask for longer text responses
- dropdown: Present options and ask user to choose
- checkboxes: Present options for selection
Track which fields are required (validations.required: true) and ensure those are collected.
4. Detect Repository Information
Determine the GitHub repository:
- First, try to detect from git remote:
git remote get-url origin - If not available, ask the user for owner/repo
5. Format Issue Body
Construct the issue body by combining the gathered information according to the template structure. For each field, use the format:
### [Field Label]
[User's response]
6. Determine Labels
Based on issue type and template, apply appropriate labels:
- Bug Report:
bug,triage - Feature Request:
feature,enhancement
Add priority-based labels if applicable: priority-low, priority-medium, priority-high, priority-critical
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.
- yesterday First seen · 274 lines · 21 tokens per session scan A 84eb62ecd14f
create-github-issue is a command published in the GitHub repository marcmodin/mcp-prompt-server (1 stars, last pushed 10mo ago), licensed MIT. It adds 21 tokens to every session and 1,673 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
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
language
Command "language" from ErisPulse/ErisPulse, covering erispulse.cli.commands.language 模块, 模块概述, 类列表 and class languagecommand(command).