agentmods.dev

speckit.taskstoissues

speckit.taskstoissues is a command for Claude Code from SpillwaveSolutions/agent-brain. It costs 21 tokens per session (300 once invoked), scanned A, a copy of speckit.taskstoissues, MIT.

A command that turns an existing feature task list into ordered GitHub issues. It first reads the project's specification files and checks that the Git remote is a GitHub repository.

In plain words
What is it for?
Use it when a feature already has specification and task documents and you want matching issues created in its GitHub repository.
Why use it?
It removes the manual work of rewriting planned tasks as actionable issues and preserves their dependency order.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: Copilot chat-mode frontmatter (tools: vscode/*).

not rated 119repo 1mo ago A scan 21 tokens copy · 89% MIT

Good fit Use it when a feature already has specification and task documents and you want matching issues created in its GitHub repository.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/spillwavesolutions/agent-brain/speckit.taskstoissues
View source ↗ SpillwaveSolutions/agent-brain
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.

Clone the repo
git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain

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/spillwavesolutions/agent-brain/speckit.taskstoissues/github.svg)](https://agentmods.dev/commands/spillwavesolutions/agent-brain/speckit.taskstoissues)
Your own site
<a href="https://agentmods.dev/commands/spillwavesolutions/agent-brain/speckit.taskstoissues"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/speckit.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.

agentmods 80×15 button for speckit.taskstoissues

Your own site · 80×15
<a href="https://agentmods.dev/commands/spillwavesolutions/agent-brain/speckit.taskstoissues"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/speckit.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 300 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 89% 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.1 $0.00021 $0.00300
Opus 5.5 $0.00008 $0.00120
Sonnet 5.5 $0.00004 $0.00060
Haiku 4.5 $0.00002 $0.00030

Measured 2mo ago against content hash 60990a1e5180, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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

This is a copy

89% identical to speckit.taskstoissues — 4 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 · 33 lines

What it actually says

Spec directory: All SDD artifacts live under .speckit/ (features, templates, scripts, memory).

User Input

$ARGUMENTS

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

Outline

  1. Run .speckit/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. 2mo ago First seen · 33 lines · 21 tokens per session scan A 60990a1e5180

Subscribe to this mod's changes

speckit.taskstoissues is a command published in the GitHub repository SpillwaveSolutions/agent-brain (119 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 300 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to speckit.taskstoissues, differing in 4 lines, and is treated as a copy.

Claude CodeGit and workflowProject managementagent-memoryagent-pluginschromadbcodexfastapi
Related

speckit.taskstoissues compared with commands from other repositories

speckit.taskstoissues next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
speckit.taskstoissuesSpillwaveSolutions/agent-brainCommand1191mo agoMITA21Claude Code
scmfirst-fluke/fullstack-starterCommand2253d agoMITA21GitHub Copilot
rmslopHKUDS/AutoMemoryCommand268d agononeA5OpenCode
release-swarmjazz-max/ruflo-hubCommand42mo agononeA0Claude Code
swarm-prjazz-max/ruflo-hubCommand42mo agononeA0Claude Code
commitmostwise/dot-claudeCommand12mo agononeA4Claude Code
release-managerayushcodes10/echo-memCommand21mo agoApache-2.0A0Claude Code