agentmods.dev

create-this-issue

create-this-issue is a skill for Claude Code, Codex from aiya000/dotfiles. It costs 75 tokens per session (1,032 once invoked), scanned A, original, MIT.

A GitHub issue-creation workflow that turns the current task into a tracked issue. A GitHub issue is a shared record of work, including its purpose, requirements, and completion conditions.

In plain words
What is it for?
Identify the task and repository, read the applicable issue template and project instructions, draft the issue, check existing labels, and create it with the GitHub command-line tool.
Why use it?
It reduces the risk of creating an issue for the wrong repository or missing the project’s templates, rules, labels, or required details.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

not rated 19repo yesterday A scan 75 tokens original MIT

Good fit Identify the task and repository, read the applicable issue template and project instructions, draft the issue, check existing labels, and create it with the GitHub command-line tool.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aiya000/dotfiles/create-this-issue
View source ↗ aiya000/dotfiles
Install

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.

Any agent
npx skills add aiya000/dotfiles --skill create-this-issue
Clone the repo
git clone --depth 1 https://github.com/aiya000/dotfiles

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for create-this-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/aiya000/dotfiles/create-this-issue/github.svg)](https://agentmods.dev/skills/aiya000/dotfiles/create-this-issue)
Your own site
<a href="https://agentmods.dev/skills/aiya000/dotfiles/create-this-issue"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/create-this-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.

agentmods 80×15 button for create-this-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/aiya000/dotfiles/create-this-issue"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/create-this-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,032 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.01032
Opus 5 $0.00037 $0.00516
Sonnet 5 $0.00015 $0.00206
Haiku 4.5 $0.00007 $0.00103

Measured today against content hash 8d53556fbb96, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

create-this-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 today.

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.

.kiro_global/skills/create-this-issue/SKILL.md · 68 lines

What it actually says

現在のタスクからIssueを作成

目的

現在のKiroセッションで取り組んでいる、または取り組む予定のタスクを、会話の文脈から特定してGitHub Issueにする。

このSkillの明示的な呼び出しはIssue作成の依頼として扱う。ただし、タスク内容、対象リポジトリ、またはテンプレート上の必須判断が不明瞭な場合は、作成前にユーザーへ確認する。

手順

1. 対象を確認する

  1. 現在のGitリポジトリとGitHub remoteを確認する
  2. ユーザーが対象リポジトリを指定している場合は、そのリポジトリを使用する
  3. gh auth status でGitHub認証を確認する
  4. 現在の会話、ユーザーの依頼、アクティブなタスクリストから、Issueにするタスクを特定する
  5. 複数の独立したタスクが混在している場合は、どれをIssueにするか確認する
  6. タスクの目的や完了条件を特定できない場合は、推測で作成せずユーザーへ確認する

2. 現行テンプレートと規約を読む

  1. Gitルートの .github/ISSUE_TEMPLATE/default.md を読む
  2. Gitルートおよび対象範囲の AGENTS.md にIssue本文の規約があれば読む
  3. テンプレートや上位規約がこのSkillの例と異なる場合は、現行ファイルを優先する

3. Issue内容を組み立てる

  • タイトル: タスク内容を簡潔に表す日本語タイトル
  • 「何に貢献するか」: タスク内容に該当する既存項目へチェックを入れる
  • 「本文」: 会話から分かる背景、目的、実装内容、完了条件、制約を具体的に記載する
  • 手動動作確認手順: 現行のリポジトリ規約で必須の場合は、非エンジニアがそのまま実行できる形式で本文冒頭に記載する
  • ラベル: タスクに適合する既存ラベルだけを候補にする

「何に貢献するか」を判断できない場合はユーザーへ確認する。関連情報が会話にない場合は、事実を創作せず省略または確認する。

4. ラベルを確認する

  1. gh label list --limit 1000 などで既存ラベルを取得する
  2. 内容と明確に一致するラベルだけを選ぶ
  3. 存在しないラベルを新規作成しない
  4. ラベルの判断が曖昧な場合は、ラベルなしで作成するかユーザーへ確認する

5. Issueを作成する

  1. Markdown本文はshell引数へ直接展開せず、gh issue create --body-file で安全に渡す
  2. gh issue create に日本語タイトル、本文、既存ラベルを指定する
  3. コマンドから返されたIssue URLと番号を記録する
  4. gh issue view <番号> --json number,title,body,labels,url で作成結果を再取得する
  5. タイトル、本文、ラベルが意図した内容と一致することを確認する

完了報告

次をユーザーへ報告する。

  • Issue番号
  • タイトル
  • URL
  • 付与したラベル
  • 作成後の検証結果

作成に失敗した場合は、重複作成を避けるためIssue一覧を確認してから再試行する。解消できない場合は、エラー内容と作成できなかった理由を報告する。

Changes

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.

  1. today First seen · 68 lines · 75 tokens per session scan A 8d53556fbb96

Subscribe to this mod's changes

create-this-issue is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 1,032 once invoked, about $0.0004 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-09-09.

Git and workflowProject managementclojuredotfilesneovimvimxmonad
Related

Other skills, from other repositories

autopilot

Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).

joshukraine/dotfiles · 40 tokens

autopilot-triage

Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.

joshukraine/dotfiles · 44 tokens

create-pr

Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.

joshukraine/dotfiles · 25 tokens

write-ticket-description

Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without invoking this skill first.

ooloth/dotfiles · 64 tokens

use-beads

Full reference for the beads task management workflow. Use when working with beads issues, planning multi-step work, or managing task lifecycle.

ooloth/dotfiles · 30 tokens

use-trekker

Full reference for the trekker task management workflow. Use when working with trekker issues, planning multi-step work, or managing task lifecycle.

ooloth/dotfiles · 33 tokens