oryxos: Skill for Claude Code

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

speckit-taskstoissues is a skill for Claude Code from oryx-labs/oryxos. It costs 28 tokens per session (1,741 once invoked), scanned A, a copy of speckit-taskstoissues, Apache-2.0.

A tool that turns an existing task list for a feature into GitHub issues arranged by dependency. GitHub issues are trackable work items used to plan and manage software changes.

In plain words
What is it for?
Use it to create actionable, ordered GitHub issues from feature tasks and available design documents.
Why use it?
It removes the manual work of rewriting tasks as issue descriptions and helps show which pieces need to be done first.

Skill for Claude Code

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

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

Reuse

Borrowing it

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

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/oryx-labs/oryxos/speckit-taskstoissues/github.svg)](https://agentmods.dev/skills/oryx-labs/oryxos/speckit-taskstoissues)
Your own site
<a href="https://agentmods.dev/skills/oryx-labs/oryxos/speckit-taskstoissues"><img src="https://agentmods.dev/badge/skills/oryx-labs/oryxos/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/oryx-labs/oryxos/speckit-taskstoissues"><img src="https://agentmods.dev/badge/skills/oryx-labs/oryxos/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,741 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.01741
Opus 5 $0.00014 $0.00870
Sonnet 5 $0.00006 $0.00348
Haiku 4.5 $0.00003 $0.00174

Measured 9d ago against content hash dfe23aaca349, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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-taskstoissues — 10 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 · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 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.
      
      After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal {command} id shown above, e.g. a skills-mode agent runs it as /skill:speckit-... or $speckit-...). Emitting the block alone does not run the hook.
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Read the full file on GitHub · 113 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. 9d ago First seen · 113 lines · 28 tokens per session scan A dfe23aaca349

Subscribe to this mod's changes

speckit-taskstoissues is a skill published in the GitHub repository oryx-labs/oryxos (156 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 1,741 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 73% identical to speckit-taskstoissues, differing in 10 lines, and is treated as a copy.

Related

Other skills, from other repositories

stale-sweep

Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…

googleapis/mcp-toolbox · 159 tokens

meta-meeting-to-workflow

Use this meta-skill instead of answering directly when the user has meeting notes, transcripts, recordings, or rough discussion notes and wants them converted into decisions, owners, follow-ups, tasks, issues, or shareable minutes through multi-skill orchestration.

opensquilla/opensquilla · 58 tokens

meta-issue-to-pr-autopilot

Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.

opensquilla/opensquilla · 117 tokens

meta-github-pr-watch-digest

Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.

opensquilla/opensquilla · 48 tokens

secretary

Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads.

ginlix-ai/LangAlpha · 21 tokens

ceo-setup

One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.

suyoumo/ClawProBench · 60 tokens