create-issue

A command that turns a feature idea, bug report, or improvement request into a structured GitHub issue. GitHub issues are shared records used to discuss and track work in a repository.

In plain words
What is it for?
Use it to research an existing repository and draft an issue with a clear title, category, and project-specific context.
Why use it?
It reduces the manual research and formatting needed to create a useful issue. It checks the repository, related issues, labels, project documents, and recent merged changes for context.

Command for Codex

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.

agentmods
npx agentmods add commands/opsmill/infrahub-mcp/create-issue
Clone the repo
git clone --depth 1 https://github.com/opsmill/infrahub-mcp

Made for: Codex.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,288 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00018 $0.01288
Opus 5 $0.00009 $0.00644
Sonnet 5 $0.00004 $0.00258
Haiku 4.5 $0.00002 $0.00129

Measured yesterday against content hash fd46566e8455, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.agents/commands/create-issue.md · 199 lines

How it starts

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

Create GitHub Issue

Introduction

Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues that follow project conventions and best practices. This command provides flexible detail levels to match your needs.

Prerequisites

  • GitHub CLI (gh) installed and authenticated
  • Current directory is within the infrahub-mcp repository

Feature Description

#$ARGUMENTS

Main Tasks

1. Repository Research & Context Gathering

  • Identify the repository and confirm access:
    gh repo view --json nameWithOwner -q '.nameWithOwner'
    
  • Check for related existing issues:
    gh issue list --state open --limit 20
    gh issue search "<keywords>" --limit 10
    
  • Review project structure for relevant context:
    • dev/constitution.md — project principles
    • dev/knowledge/architecture.md — architecture overview
    • src/infrahub_mcp/ — source code layout
  • Identify relevant labels:
    gh label list
    
  • Check recent PRs for similar patterns:
    gh pr list --state merged --limit 10
    

2. Issue Planning & Structure

Title & Categorization:

  • Draft clear, searchable issue title using conventional format (e.g., feat:, fix:, docs:)
  • Identify appropriate labels from repository's label set
  • Determine issue type: enhancement, bug, documentation, refactor
  • Consider adding priority labels if available

Stakeholder Analysis:

  • Identify who will be affected by this issue (MCP users, developers, operators)
  • Note any cross-project dependencies (infrahub-sdk, FastMCP)

Content Planning:

  • Choose appropriate detail level based on issue complexity and audience
  • List all necessary sections for the chosen template
  • Gather supporting materials (error logs, configuration examples)

Read the full file on GitHub · 199 lines

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. yesterday First seen · 199 lines · 18 tokens per session scan A fd46566e8455

Subscribe to this mod's changes

create-issue is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 4d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,288 once invoked, about $0.0001 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.