Borrowing it
Nothing to install: this file belongs to Terry-Mao/AICodingFlow. 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/Terry-Mao/AICodingFlow/main/.agents/skills/create-issue/SKILL.mdgit clone --depth 1 https://github.com/Terry-Mao/AICodingFlowWrote 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/terry-mao/aicodingflow/create-issue)<a href="https://agentmods.dev/skills/terry-mao/aicodingflow/create-issue"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/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/terry-mao/aicodingflow/create-issue"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/create-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00584 |
| Opus 5.5 | $0.00010 | $0.00234 |
| Sonnet 5.5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-issue
Use this when the user asks to create, file, open, or draft a GitHub issue.
Process
- Identify the target repository and inspect
.github/ISSUE_TEMPLATE.mdplus.github/ISSUE_TEMPLATE/markdown/YAML forms. Treatconfig.ymlonly as blank-issue/contact-link configuration, not as a template. - Select the best template from the request and its metadata. Use a plain issue only when no template fits and blank issues are allowed. Ask one short question when equally suitable templates would change required fields.
- Write only facts supplied by the user, attachments, or this conversation.
Preserve useful template headings, convert YAML form fields to markdown,
use
Not providedfor unknown required fields, and keep one issue focused on one actionable request. - Leave classification labels to automated triage. Apply labels, assignees, milestones, or projects only when the user explicitly requests them or the template requires a routing value. Do not perform a broad duplicate search before creation when automated triage is available.
- A security report (vulnerability, exploit, secret, credential, private data)
stays private by default. Check
SECURITY.mdand the repository's private reporting channel; publish only after explicit confirmation that the report is fully redacted and safe for public disclosure. - Creating an issue is an external side effect. If repository, template, title, body, and metadata are unambiguous and the user explicitly asked to create it, submit directly. Otherwise show a compact preview and confirm.
Submit
Use GitHub CLI with generated values passed as separate arguments, preferably through a temporary body file:
gh issue create --repo "$repo" --title "$title" --body-file "$body_file"
Never interpolate untrusted text into a shell command. If gh is unavailable,
unauthenticated, or unauthorized, do not fall back to gh api or raw HTTP;
report the exact repository, title, body, and metadata for manual creation.
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 · 60 lines · 24 tokens per session scan A 062b78a6b69d
create-issue is a skill published in the GitHub repository Terry-Mao/AICodingFlow (169 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 584 once invoked, about $0.0001 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…