install-github-backlog

A GitHub Issues workflow for managing development tasks inside an AI agent's repository. GitHub Issues are tracked work items attached to a repository.

In plain words
What is it for?
Use it to view backlogs and roadmaps, organise issues, run a supervised sprint, or process tasks autonomously in a work loop.
Why use it?
It turns an unstructured list of coding work into a process for prioritising, claiming, planning, implementing, and closing tasks.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/abilityai/abilities/add-backlog
Any agent
npx skills add Abilityai/abilities --skill add-backlog
Clone the repo
git clone --depth 1 https://github.com/Abilityai/abilities

Made for: Claude Code, Codex.

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,461 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.05461
Opus 5 $0.00022 $0.02730
Sonnet 5 $0.00009 $0.01092
Haiku 4.5 $0.00004 $0.00546

Measured 2d ago against content hash 99536275e52e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

install-github-backlog scanned grade B with 1 finding 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

ls .claude/skills/ 2>/dev/null
plugins/agent-dev/skills/add-backlog/SKILL.md · 739 lines

How it starts

The opening of the file, as written. The whole thing — 739 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Install GitHub Backlog

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. install-github-backlog vX.Y — recent: <summary>. Then proceed.

Add GitHub Issues task management to any Claude Code agent. This wizard creates skills directly in your agent's .claude/skills/ directory — no plugin dependency, fully self-contained.

What you get:

Skill Purpose
/backlog Priority-ordered view of open issues
/roadmap Strategic view grouped by skill area
/groom Tag issues with skill:* labels, set priorities
/claim Grab the next task, mark it in-progress
/autoplan Analyze a skill issue before implementing
/close Close an issue without a git commit
/commit Stage skill file changes, commit, close issue
/sprint Human-supervised develop cycle (one issue end-to-end)
/work-loop Autonomous processing (schedulable on Trinity)

The agent's repository becomes its task queue. Issues = work items. Skills = the units of work.


Process

Step 1: Verify Environment

git remote get-url origin 2>/dev/null

If not a git repo or no GitHub remote, stop and explain: "This skill requires a GitHub repository. Initialize with git init and gh repo create."

Step 2: Verify gh CLI

gh auth status 2>&1 | head -3

If not authenticated, tell user to run ! gh auth login and re-run.

Step 3: Check for Existing Skills

ls .claude/skills/ 2>/dev/null

List which of the target skills already exist. If any do, ask:

  • Overwrite — Replace with fresh versions
  • Skip existing — Only create missing ones
  • Cancel — Abort

Step 4: Ask Workflow Preferences

Use AskUserQuestion:

  • Header: "Work Loop Schedule"
  • Question: "How should the autonomous work-loop run?"
  • Options:
    1. Daily at 9am (0 9 * * *) — recommended
    2. Every 4 hours (0 */4 * * *)
    3. Manual only (no schedule)

Read the full file on GitHub · 739 lines

Changes

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.

  1. 2d ago First seen · 739 lines · 43 tokens per session scan B 99536275e52e

Subscribe to this mod's changes

install-github-backlog is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 43 tokens to every session and 5,461 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

mattpocock/skills · 46 tokens

setup-matt-pocock-skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

mattpocock/skills · 44 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

phuryn/pm-skills · 52 tokens

bug-triage

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

Donchitos/Claude-Code-Game-Studios · 59 tokens