Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/GocciaScript/main/.agents/skills/create-issue/SKILL.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/gocciascript/create-issue)<a href="https://agentmods.dev/skills/frostney/gocciascript/create-issue"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/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/gocciascript/create-issue"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/create-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 28 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00066 | $0.01132 |
| Opus 5.5 | $0.00026 | $0.00453 |
| Sonnet 5.5 | $0.00013 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-issue — 88% identical, 98 lines differ
How it starts
The opening of the file, as written. The whole thing — 101 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. A request to file an issue authorizes creating it once the gates below pass.
Reuse authorization and settled decisions within their scope across turns. Before a required pause, complete independent authorized work, then link the exact skill file as a Markdown link and quote the rule requiring a new decision or authority verbatim in a block quote.
Gates
- Investigate before drafting: read the applicable project instructions and vision, search open and closed issues for duplicates of the outcome as well as the mechanism, and inspect the affected code, tests, and docs.
- For material unresolved requirements or a requested interview, use the actual
registered
grill-with-docsorgrill-meloop; prefergrill-with-docs. Reuse settled decisions. If neither is available, investigate directly and ask only for missing facts that affect the issue. - 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 the current GitHub account and agent environment. Stop if either is unavailable; never guess or substitute a generic label.
Draft review
Choose the template, title, labels, and body from project evidence and create
the issue without draft approval. Show the draft for approval first only when
the user asks for it, for example with /create-issue draft or "show me the
draft first", including in a later turn; that request lasts for its stated
scope. automatic is accepted and changes nothing. Resolve a material
ambiguity by asking about that point under the gates above, not by falling back
to a full draft review.
Workflow
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +10 lines 22b7d9766cd5
- 22d ago Changed · +3 lines 3a6d218e83d0
- 26d ago Changed · +4 lines · +15 tokens per session 5834cf14afd7
- 29d ago Changed · +14 lines 1843af20354b
- 1mo 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 yesterday), licensed MIT. It adds 66 tokens to every session and 1,132 once invoked, about $0.0003 per session on Opus 5.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
record-gotchas
Capture surprises, workarounds, and rough edges hit while consuming the public surface of Prisma 8, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour…
product-direction
Judges feature requests, feature pull requests and your own proposals against a repository's written product direction, gives a cited verdict, and records each new no. Use when triaging, labelling or replying to a feature request or a feature pull request, including as an autonomous triage agent; when asked whether a…
hero-kanban-move
A yellow sticky card slides from the Doing column into Done on a warm cork-board style kanban. Function: workflow state change — productivity motion, not decorative particles.
hero-calendar-flip
A red-header desk calendar flips its page from 3 to 4. Function: date advance / ship-day marker.
hero-checklist-pop
A concrete launch checklist checks off four shipping steps while a side card explains the function. This is task-completion UI motion.
hero-metro-tick
A metro track draws across the frame, station ticks appear, and an orange train marker travels from Init to Ship. It is a timing metaphor for shipping workflows.