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/gocciascript/create-issuenpx skills add frostney/GocciaScript --skill create-issuegit clone --depth 1 https://github.com/frostney/GocciaScriptWhat 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.00649 |
| Opus 5 | $0.00026 | $0.00324 |
| Sonnet 5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-issue — 88% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 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.
- Before posting, resolve the authenticated GitHub username and exact model name from current forge and host evidence. Stop if either is unavailable; never guess or substitute a generic label.
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.
- End the issue body with this visually separate GitHub Note, replacing both values with the exact identities resolved for this run:
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 · 70 lines · 51 tokens per session scan A 73e4eb28ecc3
create-issue is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 649 once invoked, about $0.0003 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
qcad
Use when editing DXF files with a professional open-source 2D CAD application — CAM output, part libraries, isometric projection. QCAD: open-source 2D CAD with DXF as native format, scriptable via ECMAScript.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
manage-prd-docs
Automatically manage product requirements across current decisions in docs/PRD.md and docs/prd/, mature future plans under docs/plans/, and active implementation under docs/work/. Use whenever the conversation discusses, clarifies, versions, plans, implements, completes, splits, or migrates a product requirement or…
modernize-ecmascript
当 Agent 编写或修改 JavaScript、TypeScript，用户要求按指定环境、输出版本、ES20xx 或具体语法编写代码，询问某项 ECMAScript 语法、标准内置 API 或提案能否采用，或者要求审查仓库中可简化、可现代化的写法时，应使用本 Skill。围绕目标文件真实经过的解析器、转换器和输出目标判断新语法能否安全采用，并按需读取 TC39 Atlas 的提案阶段、官方仓库、polyfill 与实现线索。.
codebase-audit
Audits the current repository for systemic correctness, architecture, churn, simplification, clarity, test value, and operational risks using current source and reproducible probes. It can delegate evidence gathering across bounded capability and perspective lanes. Use when the user runs /codebase-audit or asks for an…