Borrowing it
Nothing to install: this file belongs to P2ERGmbH/agentic-coding. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/P2ERGmbH/agentic-coding/main/.agents/skills/github-sub-issue-add/SKILL.mdgit clone --depth 1 https://github.com/P2ERGmbH/agentic-codingWrote 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/p2ergmbh/agentic-coding/github-sub-issue-add)<a href="https://agentmods.dev/skills/p2ergmbh/agentic-coding/github-sub-issue-add"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/github-sub-issue-add/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.
<a href="https://agentmods.dev/skills/p2ergmbh/agentic-coding/github-sub-issue-add"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/github-sub-issue-add.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00024 | $0.01459 |
| Opus 5.5 | $0.00010 | $0.00584 |
| Sonnet 5.5 | $0.00005 | $0.00292 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
github-sub-issue-add 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 2mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Sub-Issue to GitHub Main/Parent Issue
This skill allows creating a new sub-issue or linking an existing issue as a sub-issue to a parent/main issue using the official GitHub REST API (API version 2026-03-10). It also supports establishing issue dependencies (blocking relationships).
⚠️ CRITICAL CONCEPT: GitHub Identifiers
To perform sub-issue or dependency operations, you MUST understand and handle the difference between GitHub's distinct identifier types:
- Issue Number (e.g.,
2396):- A human-friendly sequential integer unique within a single repository.
- Used in URLs, markdown references (
#2396), and standard CLI commands (gh issue view 2396).
- GraphQL Global Node ID (e.g.,
"I_kwDOP0rKb88AAAABFCwpYA"):- A globally unique string identifier.
- WARNING: In the
ghCLI, callinggh issue view <number> --json idorgh issue list --json idreturns this string Node ID, NOT the numerical database ID!
- Numerical REST Database ID (e.g.,
4633405792):- A globally unique numerical integer used by GitHub's relational database.
- CRITICAL: The REST API endpoints for sub-issues and dependencies (under API version
2026-03-10) require this numerical Database ID in their JSON payloads. Passing the sequential Issue Number or the string GraphQL Global Node ID will result in validation errors (typically404 Not Foundor422 Unprocessable Entity).
⚡ RECOMMENDED METHOD: Foolproof Helper Script
To automate ID resolution, API calls, and handle fallbacks gracefully, always use the workspace helper script:
Link Sub-Issue to Parent:
npx node .agents/skills/github-sub-issue-add/scripts/github-sub-issue-helper.js add --parent <parent-issue-number> --sub <sub-issue-number>
Establish Issue Dependency (Blocking Relationship):
npx node .agents/skills/github-sub-issue-add/scripts/github-sub-issue-helper.js dependency --dependent <dependent-issue-number> --blocking <blocking-issue-number>
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 149 lines · 24 tokens per session scan A 240fae0ee3a5
github-sub-issue-add is a skill published in the GitHub repository P2ERGmbH/agentic-coding (9 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,459 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.