github-issues-from-spec

A command that turns a specification document—a written description of requirements—into GitHub issues, which are trackable work items in a code repository.

In plain words
What is it for?
Use it to create an initial GitHub issue list from project requirements.
Why use it?
It removes the manual step of breaking a long requirements document into separate tasks.

Command for Claude Code

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/ai-digital-architect/awesome-claude-code/github-issues-from-spec
Clone the repo
git clone --depth 1 https://github.com/ai-digital-architect/awesome-claude-code

Made for: Claude Code.

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,256 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin unknown 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.00000 $0.01256
Opus 5 $0.00000 $0.00628
Sonnet 5 $0.00000 $0.00251
Haiku 4.5 $0.00000 $0.00126

Measured 2d ago against content hash 5e003478afbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

github-issues-from-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 2d 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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

- Extract secret from environment config
.claude/commands/github-issues-from-spec.md · 228 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 228 lines · 0 tokens per session scan C 5e003478afbf

Subscribe to this mod's changes

github-issues-from-spec is a command published in the GitHub repository ai-digital-architect/awesome-claude-code (1 stars, last pushed 3mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,256 tokens. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.