vibetags: Skill for Claude Code

.claude/skills/speckit-taskstoissues/SKILL.md

speckit-taskstoissues is a skill for Claude Code from PIsberg/vibetags. It costs 28 tokens per session (1,068 once invoked), scanned A, a copy of speckit-constitution, MIT.

A workflow skill that converts existing implementation tasks into ordered GitHub issues. GitHub issues are online work items used to track coding tasks, discussion, and progress.

In plain words
What is it for?
It is for publishing feature tasks as actionable GitHub issues based on the available design documents.
Why use it?
It avoids copying tasks into issue trackers by hand and preserves their dependency order when preparing work for a team.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

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

Reuse

Borrowing it

Nothing to install: this file belongs to PIsberg/vibetags. 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/PIsberg/vibetags/main/.claude/skills/speckit-taskstoissues/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/PIsberg/vibetags

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/skills/pisberg/vibetags/speckit-taskstoissues/github.svg)](https://agentmods.dev/skills/pisberg/vibetags/speckit-taskstoissues)
Your own site
<a href="https://agentmods.dev/skills/pisberg/vibetags/speckit-taskstoissues"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/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/skills/pisberg/vibetags/speckit-taskstoissues"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/speckit-taskstoissues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,068 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 73% 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.00028 $0.01068
Opus 5.5 $0.00011 $0.00427
Sonnet 5.5 $0.00006 $0.00214
Haiku 4.5 $0.00003 $0.00107

Measured 1mo ago against content hash ccacc12041d1, 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 1mo 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

73% identical to speckit-constitution — 89 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/skills/speckit-taskstoissues/SKILL.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 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).

Pre-Execution Checks

Check for extension hooks (before tasks-to-issues conversion):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_taskstoissues key
  • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
  • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
  • For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
    • If the hook has no condition field, or it is null/empty, treat the hook as executable
    • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
  • When constructing slash commands from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.
  • For each executable hook, output the following based on its optional flag:
    • Optional hook (optional: true):
      ## Extension Hooks
      
      **Optional Pre-Hook**: {extension}
      Command: `/{command}`
      Description: {description}
      
      Prompt: {prompt}
      To execute: `/{command}`
      
    • Mandatory hook (optional: false):
      ## Extension Hooks
      
      **Automatic Pre-Hook**: {extension}
      Executing: `/{command}`
      EXECUTE_COMMAND: {command}
      
      Wait for the result of the hook command before proceeding to the Outline.
      
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

  1. 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").
  2. From the executed script, extract the path to tasks.
  3. Get the Git remote by running:

Read the full file on GitHub · 107 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. 1mo ago First seen · 107 lines · 28 tokens per session scan A ccacc12041d1

Subscribe to this mod's changes

speckit-taskstoissues is a skill published in the GitHub repository PIsberg/vibetags (25 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,068 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 73% identical to speckit-constitution, differing in 89 lines, and is treated as a copy.

Related

Other skills, from other repositories

omh-agent-board

This is a Hermes-native agent-board workflow skill.

rlaope/oh-my-hermes · 69 tokens

work-summary

Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on, project health, what's blocked, where did I…

jpicklyk/task-orchestrator · 110 tokens

stakeholder-alignment

Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).

Owl-Listener/designer-skills · 45 tokens

java-spring

Build and upgrade Java/Spring services with explicit transaction, concurrency and deployment contracts. Use when implementing Spring Boot APIs, data access or jobs; verify JDK/framework/build-tool compatibility and preserve the application architecture.

WrongStack/WrongStack · 45 tokens

leadership

Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.

travisjneuman/.claude · 42 tokens

product-management

Product management expertise for product strategy, roadmap planning, feature prioritization (RICE, ICE, MoSCoW), customer research, A/B testing, product analytics, and product-market fit. Use when building product roadmaps, prioritizing features, or defining product strategy.

travisjneuman/.claude · 58 tokens