Borrowing it
Nothing to install: this file belongs to frostney/pascal-mcp-sdk. 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/frostney/pascal-mcp-sdk/main/.agents/skills/create-issue/SKILL.mdgit clone --depth 1 https://github.com/frostney/pascal-mcp-sdkWrote 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/frostney/pascal-mcp-sdk/create-issue)<a href="https://agentmods.dev/skills/frostney/pascal-mcp-sdk/create-issue"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/create-issue/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/frostney/pascal-mcp-sdk/create-issue"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/create-issue.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00564 |
| Opus 5.5 | $0.00020 | $0.00226 |
| Sonnet 5.5 | $0.00010 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
create-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 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.
This is a copy
88% identical to create-issue — 98 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create issue
Turn the user's input into an implementation-ready issue grounded in the current repository, then create it after the required review boundary.
Gates
- Investigate before drafting: read the applicable project instructions and vision, search open and closed issues for duplicates, and inspect the affected code, tests, and docs.
- When
grill-with-docsorgrill-meis registered, run its actual user-question loop before drafting. Prefergrill-with-docs. If neither is available, note that once and continue. - Stop before drafting when the request conflicts with project vision, is a duplicate, or needs material facts that cannot be established. For a duplicate, return the existing issue and stop without asking whether to file the same request anyway or mutate the existing issue.
Automatic mode
Automatic mode applies only when the original prompt says automatic or
explicitly requests it. Complete every gate, then choose the template, title,
labels, and body from project evidence and create the issue without draft
approval. Material ambiguity or risk disables automatic mode.
Workflow
- Discover the repository's issue templates and existing label conventions.
- Investigate the request using the gates above. Ground any progress claim in evidence gathered this run.
- Run the registered grill skill and incorporate the result.
- Draft against the matching template. Keep only decision-, implementation-,
and verification-relevant content:
- a specific plain-language title;
- problem, current and expected behavior, scope, constraints, and acceptance criteria;
- reproduction and regression expectations for bugs;
- user/test impact, likely affected area, and related work where relevant.
- For UI/UX work, add the affected states, current and expected visual evidence, accessibility expectations, responsive/theme scope, and applicable design system components or tokens.
- Choose only existing labels unless the user asks to create one.
- Show the proposed title, labels, and body unless the user waived review or automatic mode applies.
- Create the issue with the available forge tooling and return its URL.
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 · 61 lines · 51 tokens per session scan A 7f7f5434aaab
create-issue is a skill published in the GitHub repository frostney/pascal-mcp-sdk (2 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 564 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to create-issue, differing in 98 lines, and is treated as a copy.
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.
git-workflow
Trunk-based git workflow with worktrees, switch/restore over checkout, Conventional Commits, force-with-lease. Use whenever the user asks me to commit, push, branch, or rebase.
project-briefing
Generate an executive briefing of the last 24 hours of commits for the current project or a specified directory. Use when the user asks for a project update, daily briefing, commit summary, "what changed today," or wants to stay up-to-date with recent work.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
issue
Create a GitHub issue using the Dedalus issue templates (bug, feature, question). Injects branch and commit context automatically, prompts for Linear link. Use when creating a GitHub issue using Dedalus templates, or the user says "file an issue", "create issue", "open a bug", or "report a feature request".
oss-workflow
Open-source project success workflow for viznoir. Codifies contributor onboarding, release management (Release Please + PyPI), issue triage, and showcase curation. Triggers: release, contributor, onboarding, PyPI publish, issue triage, showcase, CHANGELOG, good first issue.