agentmods.dev

agentcmd: Command for Claude Code

.claude/commands/cmd/generate-issue-spec.md

generate-issue-spec is a command for Claude Code from jnarowski/agentcmd. It costs 8 tokens per session (2,531 once invoked), scanned C, original, MIT.

A command that writes a focused specification for one issue, bug, or small task without implementing it. The specification is saved under .agent/specs/todo/ with tasks, file paths, commands, and complexity scores.

In plain words
What is it for?
Scoping small development tasks before coding and recording the required work in a project spec.
Why use it?
It turns an informal issue into an ordered implementation plan while keeping the code unchanged.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

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

not rated 18repo 10mo ago C scan 8 tokens original MIT
View source ↗ jnarowski/agentcmd agentcmd.dev
Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/generate-issue-spec"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-issue-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,531 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00008 $0.02531
Opus 5.5 $0.00003 $0.01012
Sonnet 5.5 $0.00002 $0.00506
Haiku 4.5 $0.00001 $0.00253

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

Security

Grade C, and why

generate-issue-spec scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- prettier-ignore-start -->
.claude/commands/cmd/generate-issue-spec.md · 327 lines

How it starts

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

Issue Specification

Generate a focused spec for single issues, bugs, or small tasks. Creates structured spec at .agent/specs/todo/[id]-[issue]/spec.md with timestamp-based ID.

Variables

  • $param1: $1 (optional) - Issue context or description (infers from conversation if omitted)

Instructions

  • IMPORTANT: Use reasoning model - THINK HARD about issue scope, approach, AND complexity
  • IMPORTANT: This command ONLY generates spec - do NOT implement code or make changes beyond spec folder/file and index.json
  • Your ONLY file operations: create spec folder, write spec.md, update index.json - nothing else
  • Normalize issue name to kebab-case for folder name
  • Replace ALL <placeholders> with specific details
  • Create detailed tasks with specific file paths and commands
  • Assign complexity (1-10) to EVERY task using scale below
  • Order tasks by dependencies
  • Keep scope focused - if issue grows complex, consider /cmd:generate-spec instead
  • DO NOT include hour estimates - use complexity points only

Complexity Scale

Assign based on context window usage and cognitive load:

  • 1-2/10: Trivial - Single file, <50 lines, minimal context (config, doc, simple type)
  • 3-4/10: Simple - Few files, straightforward logic (single endpoint, basic component)
  • 5-6/10: Moderate - Multiple related files, moderate context (DB field + migration + API)
  • 7-8/10: Complex - Cross-cutting change, high context (full-stack feature, state refactor)
  • 9-10/10: Very complex - Architectural change, deep knowledge required (major refactor)

Key principle: Higher complexity = more context agent needs to load/understand

Workflow

  1. Determine Context:

    • If $param1 provided: Use as context
    • If $param1 empty: Infer from conversation history

  2. Generate Spec ID:

    • Generate timestamp-based ID in format YYMMDDHHmm using current local time
    • Example: November 13, 2025 at 2:22pm local → 2511131422
    • Read .agent/specs/index.json (will be updated in step 8)

Read the full file on GitHub · 327 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 · 327 lines · 8 tokens per session scan C f1d73fb23ad0

Subscribe to this mod's changes

generate-issue-spec is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 2,531 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Planning
Related

generate-issue-spec compared with commands from other repositories

generate-issue-spec next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
generate-issue-specjnarowski/agentcmdCommand1810mo agoMITC8Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code