speckit.taskstoissues

speckit.taskstoissues is a command for Claude Code from steiner385/mcp-git-issue-priority. It costs 21 tokens per session (272 once invoked), scanned A, a copy of speckit.taskstoissues, MIT.

A command that turns an existing feature task list into GitHub issues, which are work items stored in a Git repository's project tracker. It orders the issues according to their dependencies.

In plain words
What is it for?
Use it when a feature already has design materials and tasks, and you want matching issues created in the repository's GitHub project.
Why use it?
It removes the manual work of rewriting tasks into separate, actionable issues and helps preserve the order in which dependent work should happen.

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/steiner385/mcp-git-issue-priority/speckit.taskstoissues
Clone the repo
git clone --depth 1 https://github.com/steiner385/mcp-git-issue-priority

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 speckit.taskstoissues

README.md
[![agentmods](https://agentmods.dev/badge/commands/steiner385/mcp-git-issue-priority/speckit.taskstoissues.svg)](https://agentmods.dev/commands/steiner385/mcp-git-issue-priority/speckit.taskstoissues)
Your own site
<a href="https://agentmods.dev/commands/steiner385/mcp-git-issue-priority/speckit.taskstoissues"><img src="https://agentmods.dev/badge/commands/steiner385/mcp-git-issue-priority/speckit.taskstoissues.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 272 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00021 $0.00272
Opus 5 $0.00010 $0.00136
Sonnet 5 $0.00004 $0.00054
Haiku 4.5 $0.00002 $0.00027

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

Security

Grade A, and why

speckit.taskstoissues 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 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.

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.

Origin

This is a copy

100% identical to speckit.taskstoissues — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/speckit.taskstoissues.md · 31 lines

What it actually says

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

  1. Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
  2. From the executed script, extract the path to tasks.
  3. Get the Git remote by running:
git config --get remote.origin.url

[!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL

  1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.

[!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL

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 · 31 lines · 21 tokens per session scan A 23f5098f197d

Subscribe to this mod's changes

speckit.taskstoissues is a command published in the GitHub repository steiner385/mcp-git-issue-priority (0 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 272 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.taskstoissues, differing in 0 lines, and is treated as a copy.