Borrowing it
Nothing to install: this file belongs to nanotaboada/go-samples-gin-restful. 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/nanotaboada/go-samples-gin-restful/master/.claude/skills/create-issue/SKILL.mdgit clone --depth 1 https://github.com/nanotaboada/go-samples-gin-restfulWrote 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/nanotaboada/go-samples-gin-restful/create-issue)<a href="https://agentmods.dev/skills/nanotaboada/go-samples-gin-restful/create-issue"><img src="https://agentmods.dev/badge/skills/nanotaboada/go-samples-gin-restful/create-issue.svg" alt="Measured on agentmods" 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.00031 | $0.00224 |
| Opus 5 | $0.00015 | $0.00112 |
| Sonnet 5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
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 6d 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.
What it actually says
Create Issue
Draft a GitHub Issue using the template matching the work type.
Feature request (enhancement, go labels):
- Problem: the pain point being solved
- Proposed Solution: expected behavior and functionality
- Suggested Approach (optional): implementation plan if known
- Acceptance Criteria: at minimum — behaves as proposed, tests added/updated, no regressions
- References: related issues, docs, or examples
Bug report (bug, go labels):
- Description: clear summary of the bug
- Steps to Reproduce: numbered, minimal steps
- Expected / Actual Behavior: one section each
- Environment: runtime versions + OS
- Additional Context: logs, screenshots, stack traces
- Possible Solution (optional): suggested fix or workaround
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.
- 6d ago First seen · 24 lines · 31 tokens per session scan A d4c5f62d5d28
create-issue is a skill published in the GitHub repository nanotaboada/go-samples-gin-restful (2 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 224 once invoked, about $0.0002 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 skills, from other repositories
material-ui-nextjs
Integrates Material UI with Next.js App and Pages routers using @mui/material-nextjs, Emotion cache providers, next/font, CSS layers with Tailwind/CSS Modules, Link component prop patterns, CSS theme variables SSR notes, and App Router useSearchParams + Suspense. Use when setting up or debugging MUI in a Next.js app.
RootCauseAnalysis
Structured incident investigation using Five Whys, Fishbone, blameless Postmortem, Fault Tree, Kepner-Tregoe, and FMEA — traces failures to systemic root causes rather than blaming humans. USE WHEN root cause, RCA, 5 whys, fishbone, postmortem, incident analysis, fault tree, why does this keep failing, blameless…
Vitals
Read-only macOS performance inspection: a deterministic CLI gathers the numbers, Interpretation.md turns them into a diagnosis instead of a data dump.
benchmark-workflow
Run, diagnose, or change Xberg extraction benchmarks, quality scoring, benchmark fixtures, artifact contracts, and independently sourced ground truth. Load for the Benchmarks workflow or benchmark-harness work, not ordinary unit tests.
verified-script-execution
Fallback workflow for reliable file creation and verification when automated code execution fails.
verify-success-after-unknown-error
Verify task completion by checking filesystem state when executecodesandbox or runshell return misleading unknown errors.