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/posit-dev/py-shiny/sub-issuenpx skills add posit-dev/py-shiny --skill sub-issuegit clone --depth 1 https://github.com/posit-dev/py-shinyWhat 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.00049 | $0.00726 |
| Opus 5 | $0.00024 | $0.00363 |
| Sonnet 5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Sub-Issue Management
Manage GitHub sub-issues (child issues) using native gh CLI commands (v2.94.0+).
Prerequisites
Before using any sub-issue commands, verify the gh CLI is v2.94.0 or newer:
gh --version
If the version is older than 2.94.0, the native sub-issue flags (--parent, --add-sub-issue, --remove-sub-issue, --remove-parent) will not be available. In that case, advise the user to upgrade gh before proceeding.
Commands
Create a new sub-issue
Create a new issue directly linked as a child of a parent issue:
gh issue create --parent <parent-issue> --title "<title>" --body "<body>" --repo posit-dev/py-shiny
Flags:
--parent— Parent issue number or URL (required for sub-issue linking)--title— Title for new sub-issue (required)--body— Body text for the sub-issue--label— Comma-separated labels--assignee— Comma-separated usernames--milestone— Milestone name or number--project— Project to add the issue to
Add an existing issue as a sub-issue
gh issue edit <parent-issue> --add-sub-issue <child-issue> --repo posit-dev/py-shiny
Set or change the parent of an issue
gh issue edit <child-issue> --parent <parent-issue> --repo posit-dev/py-shiny
List sub-issues of a parent
gh issue view <parent-issue> --json subIssues,subIssuesSummary --repo posit-dev/py-shiny
Remove a sub-issue link
gh issue edit <parent-issue> --remove-sub-issue <child-issue> --repo posit-dev/py-shiny
Remove parent from an issue
gh issue edit <child-issue> --remove-parent --repo posit-dev/py-shiny
Usage Notes
- Always include
--repo posit-dev/py-shinyto ensure correct repository context - When creating multiple sub-issues, create them sequentially to avoid rate limiting
- Use
--bodywith heredoc for multi-line descriptions:
gh issue create --parent 123 --title "My issue" --body "$(cat <<'EOF'
Description here.
**Acceptance criteria:**
1. First item
2. Second item
EOF
)" --repo posit-dev/py-shiny
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.
- 2d ago First seen · 88 lines · 49 tokens per session scan A 9efccfef7c07
sub-issue is a skill published in the GitHub repository posit-dev/py-shiny (1,750 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 726 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.