add-sub-issue

add-sub-issue is a skill for Claude Code, Codex from qauth-labs/qauth. It costs 21 tokens per session (692 once invoked), scanned A, original, Apache-2.0.

A procedure for creating parent-child links between GitHub issues, so one issue can contain related sub-issues.

In plain words
What is it for?
Use it to add or remove GitHub sub-issues through the GraphQL API and GitHub CLI.
Why use it?
It gives a project hierarchy that shows how smaller pieces of work belong to a larger issue.

Skill for Claude CodeCodex

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 skills/qauth-labs/qauth/add-sub-issue
Any agent
npx skills add qauth-labs/qauth --skill add-sub-issue
Clone the repo
git clone --depth 1 https://github.com/qauth-labs/qauth

Made for: Claude Code, Codex.

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 add-sub-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/qauth-labs/qauth/add-sub-issue.svg)](https://agentmods.dev/skills/qauth-labs/qauth/add-sub-issue)
Your own site
<a href="https://agentmods.dev/skills/qauth-labs/qauth/add-sub-issue"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/add-sub-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 692 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.00692
Opus 5 $0.00010 $0.00346
Sonnet 5 $0.00004 $0.00138
Haiku 4.5 $0.00002 $0.00069

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

Security

Grade A, and why

add-sub-issue 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 5d 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.

.claude/skills/add-sub-issue/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.

Add Sub-Issue (Parent/Child Relationship)

Create parent-child relationships between GitHub issues.

Your Task

Link issues in a hierarchical structure using GitHub's sub-issues feature.

Prerequisites

Sub-issues require the GraphQL API with a feature flag.

Get Issue IDs

First, get the internal IDs for both issues:

# Get parent issue ID
PARENT_ID=$(gh issue view {parent_number} --json id --jq ".id")
echo "Parent ID: $PARENT_ID"

# Get child issue ID
CHILD_ID=$(gh issue view {child_number} --json id --jq ".id")
echo "Child ID: $CHILD_ID"

Add Sub-Issue

gh api graphql \
  -H "GraphQL-Features: sub_issues" \
  -f query='
    mutation($parentId: ID!, $childId: ID!) {
      addSubIssue(input: { issueId: $parentId, subIssueId: $childId }) {
        issue { title number }
        subIssue { title number }
      }
    }
  ' \
  -f parentId="$PARENT_ID" \
  -f childId="$CHILD_ID"

Remove Sub-Issue

gh api graphql \
  -H "GraphQL-Features: sub_issues" \
  -f query='
    mutation($parentId: ID!, $childId: ID!) {
      removeSubIssue(input: { issueId: $parentId, subIssueId: $childId }) {
        issue { title }
        subIssue { title }
      }
    }
  ' \
  -f parentId="$PARENT_ID" \
  -f childId="$CHILD_ID"

List Sub-Issues of a Parent

PARENT_ID=$(gh issue view {parent_number} --json id --jq ".id")

gh api graphql \
  -H "GraphQL-Features: sub_issues" \
  -f query='
    query($id: ID!) {
      node(id: $id) {
        ... on Issue {
          title
          number
          subIssues(first: 50) {
            nodes {
              number
              title
              state
            }
          }
        }
      }
    }
  ' \
  -f id="$PARENT_ID"

Workflow: Create Epic with Sub-Issues

  1. Create the parent (epic) issue and the child issues with the create-issue skill (which follows github-conventions for titles/labels/milestones).
  2. Fetch each issue's internal ID and link children to the parent with the addSubIssue mutation above.

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. 5d ago First seen · 113 lines · 21 tokens per session scan A 75dbf751e161

Subscribe to this mod's changes

add-sub-issue is a skill published in the GitHub repository qauth-labs/qauth (24 stars, last pushed 5d ago), licensed Apache-2.0. It adds 21 tokens to every session and 692 once invoked, about $0.0001 per session on Opus 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.