agentmods.dev

create-issues

create-issues is a skill for Claude Code from FradSer/dotclaude. It costs 54 tokens per session (805 once invoked), scanned A, original, MIT.

A process for creating GitHub issues, which are shared records of bugs, requirements, and development tasks. TDD, or test-driven development, means defining tests or expected behavior as part of the change process.

In plain words
What is it for?
Use it to file bugs, requirements, larger work items, or tasks linked to a pull request after checking the repository and existing issues.
Why use it?
It helps turn a request into a properly scoped, labeled issue that fits the repository's workflow.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the github plugin — 4 skills shipped together

not rated 594repo +1 8d ago A scan SkillSpector: pass 54 tokens original MIT

Good fit Use it to file bugs, requirements, larger work items, or tasks linked to a pull request after checking the repository and existing issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fradser/dotclaude/create-issues
View source ↗ FradSer/dotclaude dotclaude.frad.me
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 FradSer/dotclaude --skill create-issues
Clone the repo
git clone --depth 1 https://github.com/FradSer/dotclaude

Made for: Claude Code.

Or install github, the plugin that ships this one along with the rest of its 4 skills.

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-issues

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fradser/dotclaude/create-issues"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/create-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 805 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00054 $0.00805
Opus 5.5 $0.00022 $0.00322
Sonnet 5.5 $0.00011 $0.00161
Haiku 4.5 $0.00005 $0.00081

Measured 1mo ago against content hash dca004720d2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-issues 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.

github/skills/create-issues/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create GitHub Issues

Execute automated GitHub issue creation workflow for $ARGUMENTS following TDD principles and conventional commit standards.

Context

  • Current git status: !git status
  • Current branch: !git branch --show-current
  • Open issues: !gh issue list --state open --limit 10
  • GitHub authentication: !gh auth status

Requirements Summary

Follow TDD principles, conventional commits, and protected branch workflows. Use proper labels, auto-closing keywords, and atomic commits. See references/requirements.md for complete standards.

Phase 1: Repository Analysis

Goal: Assess repository state, detect templates, and determine issue scope and type.

Actions:

  1. Analyze current branch from context (main/develop vs PR branch)
  2. Review open issues to identify duplicates or related work
  3. Check for contributing guidelines (CONTRIBUTING.md) and follow its requirements
  4. Detect issue templates in .github/ISSUE_TEMPLATE/ directory
  5. If templates exist: select appropriate template using gh issue create --list
  6. Determine issue type (epic, PR-scoped, or review) based on $ARGUMENTS complexity
  7. Apply branch-based decision logic from references/decision-logic.md

See references/repository-templates.md for template detection and compliance details.

Phase 2: Issue Creation

Goal: Create GitHub issue with proper structure, labels, and links.

Actions:

  1. Create or verify required priority labels exist (see references/decision-logic.md for commands)
  2. Draft issue following structure requirements in references/issue-structure.md
  3. Apply appropriate labels (priority, type) using --label
    • Assign owners using --assignee
    • Link milestones using --milestone or projects using --project if requested
  4. Add auto-closing keywords if PR-scoped issue (NOT for epics)
    • CRITICAL: auto-closing keywords only fire when the PR merges into the repository's default branch. If the issue will be resolved by a PR targeting a non-default branch, warn the user that the issue will NOT close automatically and must be closed manually — see references/auto-closing-keywords.md for the full rule and keyword table.
  5. Link to related issues or epics if applicable

Read the full file on GitHub · 71 lines

Files

What ships with it

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

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. 1mo ago First seen · 71 lines · 54 tokens per session scan A dca004720d2d

Subscribe to this mod's changes

create-issues is a skill published in the GitHub repository FradSer/dotclaude (594 stars, last pushed 8d ago), licensed MIT. It adds 54 tokens to every session and 805 once invoked, about $0.0002 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.

Project managementTDDTestingclaude
Related

Other skills, from other repositories

conductor-implement

Execute tasks from a track's implementation plan following TDD workflow.

rmyndharis/antigravity-skills · 17 tokens

gh-issue

Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…

apache/skywalking-banyandb · 91 tokens

implement-feature

Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.

HoangNguyen0403/agent-skills-standard · 25 tokens

product

Consolidated Galyarder Framework Product intelligence bundle.

skillmds/skillmd · 13 tokens

ring:implementing-tasks

Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…

LerianStudio/ring · 103 tokens

linear-implement

This skill should be used when implementing features from Linear issues with full TDD workflow, automated planning, parallel code reviews (security and Rails best practices), systematic feedback implementation, and automated PR creation with Linear integration. Use when the user provides a Linear issue ID (e.g.…

dgalarza/claude-code-workflows · 80 tokens