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.
npx agentmods add skills/qauth-labs/qauth/add-sub-issuenpx skills add qauth-labs/qauth --skill add-sub-issuegit clone --depth 1 https://github.com/qauth-labs/qauthWrote 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.
[](https://agentmods.dev/skills/qauth-labs/qauth/add-sub-issue)<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>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 | $0.00021 | $0.00692 |
| Opus 5 | $0.00010 | $0.00346 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
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.
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
- Create the parent (epic) issue and the child issues with the
create-issueskill (which followsgithub-conventionsfor titles/labels/milestones). - Fetch each issue's internal ID and link children to the parent with the
addSubIssuemutation above.
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.
- 5d ago First seen · 113 lines · 21 tokens per session scan A 75dbf751e161
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.
Other skills, from other repositories
update-portal-ui
Guidelines for updating or designing pages in the portal React frontend (portal/src). Covers component conventions, link rendering rules, i18n patterns, and common pitfalls.
write-e2e-test
Write end-to-end (e2e) tests for authgear-server. Use when the user asks to write, add, or create e2e tests. The tests live in e2e/tests/ and are YAML-driven.
add-portal-screen
Add screens or components to the portal frontend. Use when the user asks to create a new portal page, screen, tab, or UI component.
api-design
Review or design APIs for Authgear. In review mode, evaluates a design draft against the checklist. In ideation mode, develops a design from a description and self-reviews it.
new-siteadmin-api
Full pipeline for adding a new Site Admin API feature — from OpenAPI spec through implementation plan to working service. Use when adding a new endpoint or filling in real data for an existing stub.
update-feature-config
Add or change a feature config field/section in pkg/lib/config (authgear.features.yaml). Use when adding a new feature config field, adding a new top-level section, or touching an existing section's Merge implementation.