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/sponge-b0b/polaris/github-issue-dependenciesnpx skills add sponge-b0b/Polaris --skill github-issue-dependenciesgit 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.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.00057 | $0.01183 |
| Opus 5 | $0.00028 | $0.00592 |
| Sonnet 5 | $0.00011 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00118 |
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 3d 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 — 124 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 dependency mutations for same-lineage Spec prerequisites after it has established semantic ownership and cycle safety;$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.
Do not let this helper decide whether a dependency is semantically required, where it belongs, or which lifecycle owns it.
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.
Example:
gh issue create \
--title "..." \
--body "..." \
--parent <native_parent_issue_number> \
--blocked-by <blocker_1_number>,<blocker_2_number> \
--label ready-for-agent
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.
- 3d 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 4d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,183 once invoked, about $0.0003 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-31.
Other skills, from other repositories
hybrid-ralph
Hybrid architecture combining Ralph's PRD format with Planning-with-Files' structured approach. Auto-generates PRDs from task descriptions, manages parallel story execution with dependency resolution, and provides context-filtered agents for efficient multi-story development.
mega-plan
Project-level multi-task orchestration system. Manages multiple hybrid:worktree features in parallel with dependency resolution, coordinated PRD generation, and unified merge workflow.
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
dos-dispatch-loop
Run recurring dos-dispatch cycles, switching to dos-replan when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.