rover: Command for Claude Code

.claude/commands/create-issue.md

create-issue is a command for Claude Code from endorhq/rover. It costs 0 tokens per session (1,582 once invoked), scanned A, original, Apache-2.0.

A step-by-step command for creating a new GitHub issue in the current repository.

In plain words
What is it for?
Use it when you want to turn a development request into a GitHub issue. The process collects requirements, confirms the scope, and then creates the issue.
Why use it?
It makes sure the task is described, placed in the right project context, and expanded into a concise issue before creation.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is endorhq/rover's own configuration. It tells Claude Code how to work on rover 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 rover configures →

Reuse

Borrowing it

Nothing to install: this file belongs to endorhq/rover. 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/endorhq/rover/main/.claude/commands/create-issue.md
Clone the repo
git clone --depth 1 https://github.com/endorhq/rover

Made for: Claude Code.

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/endorhq/rover/create-issue/github.svg)](https://agentmods.dev/commands/endorhq/rover/create-issue)
Your own site
<a href="https://agentmods.dev/commands/endorhq/rover/create-issue"><img src="https://agentmods.dev/badge/commands/endorhq/rover/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/endorhq/rover/create-issue"><img src="https://agentmods.dev/badge/commands/endorhq/rover/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 1,582 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.01582
Opus 5.5 $0.00000 $0.00633
Sonnet 5.5 $0.00000 $0.00316
Haiku 4.5 $0.00000 $0.00158

Measured 2mo ago against content hash 0f3b5addced2, 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 2mo 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 · 170 lines

How it starts

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

Create a new GitHub issue

Create a new GitHub issue in the current repository. This command is a process, so you must go through all the steps and wait for user input when required. You can clearly identify when you must wait for user input based on the template. This is very important.

This command has three phases:

  • Get user requirements and task description
  • Identify the task context
  • Create the issue

You must complete the three phases in order.

Phase: Get user requirements and task description

  1. Ask the user to briefly describe the task they want to accomplish.

  2. Based on the user input and your current understanding of the project (from Claude.md and any other file you consider), provide an expanded and more complete 1–2 paragraphs about the scope and the end goal of the task. Max 250 characters.

    update the website dark palette to use cyan as the base color instead of green.

    Expanded task description:

    Update the website’s dark color palette by switching the base color from green (previously defined in app.css) to cyan. Make sure the updated palette maintains enough contrast to comply with accessibility standards.

    update the website dark palette to use cyan as the base color instead of green.

    Expanded task description:

    Update the website palette to cyan.

    update the website dark palette to use cyan as the base color instead of green.

    Expanded task description:

    The goal of this task is to update the website’s dark theme color palette so that it reflects a new branding direction. At the moment, in the app.css file, the primary color that is defined is a shade that is close to green, which has been used as the base color for some time.

    However, the design team has decided to move away from this greenish hue and instead adopt cyan as the foundation for the new color palette. As part of this task, you will need to replace the previous references to the green-based primary color with the new cyan-based palette across the dark theme styles.

  3. Ask the user if this task description is good enough or if they want to add more details or change anything.

  4. If the user accepts the task description, you can finish this phase. If not, ask the user to provide more instructions () and go back to step 3.

Read the full file on GitHub · 170 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. 2mo ago First seen · 170 lines · 0 tokens per session scan A 0f3b5addced2

Subscribe to this mod's changes

create-issue is a command published in the GitHub repository endorhq/rover (273 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,582 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.

Related

create-issue compared with commands from other repositories

create-issue next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-issueendorhq/roverCommand2737mo agoApache-2.0A0Claude Code
eg-precommit-reviewvshvedov/elephant-goldfishCommand922d agoMITA24Claude Code
tldr-commit0p9b/TLDRCommand222mo agoMITA20Claude Code
gpd:branch-hypothesispsi-oss/get-physics-doneCommand9733mo agononeA19Claude Code
gpd:quickpsi-oss/get-physics-doneCommand9733mo agononeA25Claude Code
gpd:record-backtrackpsi-oss/get-physics-doneCommand9733mo agononeA26Claude Code
gpd:reapply-patchespsi-oss/get-physics-doneCommand9733mo agononeA17Claude Code