What is sp.taskstoissues?

A command that turns an existing task list into ordered GitHub issues. GitHub issues are trackable work items attached to a software repository.

Use it when a feature has completed design artifacts and tasks, to create issues in the repository named by its Git remote, but only when that remote is on GitHub.

It removes the manual work of copying tasks into issues and arranging them around their dependencies.

How AbdullahMalik17/Voice-Assistant17 configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AbdullahMalik17/Voice-Assistant17. 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/AbdullahMalik17/Voice-Assistant17/main/.claude/commands/sp.taskstoissues.md

Clone the repo

git clone --depth 1 https://github.com/AbdullahMalik17/Voice-Assistant17

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/abdullahmalik17/voice-assistant17/sp.taskstoissues/github.svg)](https://agentmods.dev/commands/abdullahmalik17/voice-assistant17/sp.taskstoissues)

Your own site

<a href="https://agentmods.dev/commands/abdullahmalik17/voice-assistant17/sp.taskstoissues"><img src="https://agentmods.dev/badge/commands/abdullahmalik17/voice-assistant17/sp.taskstoissues/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/abdullahmalik17/voice-assistant17/sp.taskstoissues"><img src="https://agentmods.dev/badge/commands/abdullahmalik17/voice-assistant17/sp.taskstoissues.svg" alt="Reviewed on agentmods" width="80" 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 629 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.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.00629
Opus 5.5	$0.00008	$0.00252
Sonnet 5.5	$0.00004	$0.00126
Haiku 4.5	$0.00002	$0.00063

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

Security

Grade A, and why

sp.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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

sp.taskstoissues — 100% identical, 112 lines differ

.claude/commands/sp.taskstoissues.md · 57 lines

How it starts

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

User Input

$ARGUMENTS

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

Outline

Run .specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks 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").
From the executed script, extract the path to tasks.
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

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

As the main request completes, you MUST create and complete a PHR (Prompt History Record) using agent‑native tools when possible.

Determine Stage
- Stage: constitution | spec | plan | tasks | red | green | refactor | explainer | misc | general
Generate Title and Determine Routing:
- Generate Title: 3–7 words (slug for filename)
- Route is automatically determined by stage:
  - constitution → history/prompts/constitution/
  - Feature stages → history/prompts/<feature-name>/ (spec, plan, tasks, red, green, refactor, explainer, misc)
  - general → history/prompts/general/
Create and Fill PHR (Shell first; fallback agent‑native)
- Run: .specify/scripts/bash/create-phr.sh --title "<title>" --stage <stage> [--feature <name>] --json
- Open the file and fill remaining placeholders (YAML + body), embedding full PROMPT_TEXT (verbatim) and concise RESPONSE_TEXT.
- If the script fails:
  - Read .specify/templates/phr-template.prompt.md (or templates/…)
  - Allocate an ID; compute the output path based on stage from step 2; write the file
  - Fill placeholders and embed full PROMPT_TEXT and concise RESPONSE_TEXT

Read the full file on GitHub · 57 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.

2mo ago First seen · 57 lines · 21 tokens per session scan A 0ab3e58e0e6a

Subscribe to this mod's changes

sp.taskstoissues is a command published in the GitHub repository AbdullahMalik17/Voice-Assistant17 (11 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 629 once invoked, about $0.0001 per session on Opus 5.5. 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.

Project management

sp.taskstoissues next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sp.taskstoissuesAbdullahMalik17/Voice-Assistant17	Command	11	4mo ago	MIT	A	21	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

Voice-Assistant17: Command for Claude Code