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/frostney/pascal-mcp-sdk/create-issuenpx skills add frostney/pascal-mcp-sdk --skill create-issuegit clone --depth 1 https://github.com/frostney/pascal-mcp-sdkWhat 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.00051 | $0.00564 |
| Opus 5 | $0.00026 | $0.00282 |
| Sonnet 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 2d 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 — 11 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.
- 2d 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 6d ago), licensed MIT. It adds 51 tokens to every session and 564 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to create-issue, differing in 11 lines, and is treated as a copy.
Other skills, from other repositories
prepare-release
Run all GocciaScript release-preparation tasks before /create-release — verify the build is green, sync docs and the website to source truth (numbers and claims), preview the changelog, run the conformance and generated-data checks, and open a prep PR — ending strictly before the version/changelog/tag work that…
profile-report-review
Review GocciaScript retained VM profile reports from test262 and benchmark main-CI runs. Use when Codex is asked to inspect uploaded test262 or benchmark performance/profile artifacts, compare week-over-week or main-run trends, investigate aggregate/detailed profile data, or turn profiling findings into compiler…
gocciascript-issue-validation
Validate GocciaScript engine issues against the project-specific test262 harness. Use alongside implement-issue for GocciaScript issues that mention test262, ECMA-262/ECMA-402 conformance, Intl, or parser compatibility flags.
implement-idea
Turns an unfiled idea into a confirmed mini-spec, implements and validates the selected approach, reviews it, and opens a draft pull request. Use when the user runs /implement-idea or asks to build something without an existing issue.
implement-issue
Validates and implements a GitHub issue against current repository evidence, runs the project's completion gate, reviews the change, and opens a draft pull request. Use when the user runs /implement-issue with an issue number.
review-pr
Resolves current pull-request review findings in place, validates and pushes fixes, and can autonomously converge and merge an opted-in pull request. Use when the user runs /review-pr or /review-pr automatic-merge.