Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. 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/sponge-b0b/Polaris/main/.agents/skills/github-issue-dependencies/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/github-issue-dependencies)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/github-issue-dependencies"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/github-issue-dependencies/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/sponge-b0b/polaris/github-issue-dependencies"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/github-issue-dependencies.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.00057 | $0.01254 |
| Opus 5.5 | $0.00023 | $0.00502 |
| Sonnet 5.5 | $0.00011 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
github-issue-dependencies 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 1mo 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Dependencies
This is a mechanical relationship helper, not a semantic lifecycle owner and not a standalone Human Handoff.
Authorized callers:
$to-specs— native Spec dependency mutations after it has established semantic ownership and cycle safety. This includes same-Wayfinder-lineage Spec prerequisites and every Spec prerequisite where either endpoint is intentionally Independent;$to-tickets— native direct-decomposition hierarchy plus dependency edges it already owns;$project-delivery-management— nativeblocked by/blockingmutations only after it has established cross-Wayfinder semantic ownership, lowest-accurate placement, and cycle safety. Both dependency endpoints must be Wayfinder-managed.
Do not let this helper decide whether a dependency is semantically required, where it belongs, which lifecycle owns it, or whether a Spec is Wayfinder-managed versus Independent.
Native gh flags
As of gh CLI v2.94.0 (June 2026), gh issue create supports:
--parent <number>— creates the new issue as a native sub-issue of<number>;--blocked-by <numbers>— marks the new issue as blocked by the given issue number(s)/URL(s), comma-separated for multiple;--blocking <numbers>— marks the new issue as blocking the given issue number(s)/URL(s);--type <name>— sets the issue type, if your tracker uses GitHub's issue types.
All four flags can be combined in one call.
$to-tickets hierarchy invariant
Only $to-tickets may use this helper to establish direct-decomposition parentage during ticket publication/reconciliation.
Resolve <native_parent_issue_number> from the artifact directly decomposed by $to-tickets:
- ordinary Spec ticketing → the Spec issue number;
- Spec Review remediation → the Spec Review issue number.
Do not substitute an upstream provenance issue for the direct decomposition parent. In particular, a remediation ticket's originating Parent Spec remains lifecycle/branch provenance and is not its native GitHub parent.
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.
- 1mo ago Changed · -1 lines 9485fc0a2de3
- 1mo ago First seen · 124 lines · 57 tokens per session scan A 8722ea4f3303
github-issue-dependencies is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 1,254 once invoked, about $0.0002 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…