metaswarm: Command for Claude Code

.claude/commands/create-issue.md

create-issue is a command for Claude Code from dsifry/metaswarm. It costs 0 tokens per session (656 once invoked), scanned A, original, MIT.

A command for creating a structured GitHub issue from a feature, bug, or refactoring description. It gathers details and includes a test-first implementation plan; TDD means writing tests before the code they check.

In plain words
What is it for?
Use it to create labelled issues with specifications, schemas or API details, TDD steps, acceptance criteria, and instructions for completing the pull-request lifecycle.
Why use it?
It turns a short request into a shared plan with clear scope, technical details, error cases, files, and acceptance checks, reducing ambiguity for people and coding agents.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is dsifry/metaswarm's own configuration. It tells Claude Code how to work on metaswarm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything metaswarm configures →

Part of the metaswarm plugin — 14 skills, 16 commands, 2 hooks shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to dsifry/metaswarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dsifry/metaswarm/main/.claude/commands/create-issue.md
Clone the repo
git clone --depth 1 https://github.com/dsifry/metaswarm

Made for: Claude Code.

Or install metaswarm, the plugin that ships this one along with the rest of its 14 skills, 16 commands, 2 hooks.

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

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

agentmods 80×15 button for create-issue

Your own site · 80×15
<a href="https://agentmods.dev/commands/dsifry/metaswarm/create-issue"><img src="https://agentmods.dev/badge/commands/dsifry/metaswarm/create-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 656 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.00000 $0.00656
Opus 5.5 $0.00000 $0.00262
Sonnet 5.5 $0.00000 $0.00131
Haiku 4.5 $0.00000 $0.00066

Measured 1mo ago against content hash 4a9f2a3a17e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.claude/commands/create-issue.md · 105 lines

How it starts

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

Create GitHub Issue

Create a comprehensive, well-structured GitHub issue with embedded agent instructions for autonomous PR lifecycle management.

Usage

/create-issue [type] [description]

Arguments (optional - will prompt if not provided):

  • type: feature, bug, or refactor
  • description: Brief description of the issue

Examples

# Interactive mode (prompts for all details)
/create-issue

# With type specified
/create-issue feature

# With type and description
/create-issue bug "Login fails when email contains plus sign"

What This Does

  1. Gathers context through interactive questions
  2. Generates comprehensive issue with all required sections:
    • Problem/Feature specification with clear scope
    • Technical specification (types, schemas, APIs)
    • TDD Implementation Plan with test-first cycles
    • Error handling matrix
    • Files to create/modify
    • Acceptance criteria checklist
    • Agent Instructions for complete PR lifecycle
  3. Creates GitHub issue with appropriate labels
  4. Returns issue number for tracking

Steps

  1. Activate the create-issue skill: Load and follow the create-issue skill definition.

  2. Gather information through the interactive flow:

    • Issue type (Feature/Bug/Refactor)
    • Brief description
    • Complexity estimate
    • Related files/services
  3. Generate issue content using appropriate template

  4. Create issue via gh issue create

Why Agent Instructions Matter

Every issue includes an "Agent Instructions" section that ensures:

  • Complete lifecycle: From implementation through merge
  • All comments addressed: Including trivial/nitpicks and out-of-scope
  • Individual responses: Every thread gets a reply
  • Iteration until done: Wait for reviews, iterate, don't auto-resolve
  • Issue creation for deferred work: > 1 day = new issue

This makes issues self-contained work packets that agents can execute autonomously while maintaining quality standards.

Read the full file on GitHub · 105 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. 1mo ago First seen · 105 lines · 0 tokens per session scan A 4a9f2a3a17e8

Subscribe to this mod's changes

create-issue is a command published in the GitHub repository dsifry/metaswarm (421 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 656 tokens. 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.