automate-github-issues

automate-github-issues is a skill for Claude Code from google-labs-code/jules-skills. It costs 22 tokens per session (982 once invoked), scanned C, original, Apache-2.0.

An automated workflow for reviewing open GitHub issues, turning them into coding tasks, and sending those tasks to parallel Jules coding agents. It runs through GitHub Actions or locally and then merges the resulting pull requests.

In plain words
What is it for?
Use it to triage open issues, create self-contained implementation plans, start separate coding sessions, check for overlapping files, and merge completed pull requests with CI checks.
Why use it?
It removes much of the manual work of reading issues, planning fixes, coordinating agents, and checking for file conflicts before merging changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to triage open issues, create self-contained implementation plans, start separate coding sessions, check for overlapping files, and merge completed pull requests with CI checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/google-labs-code/jules-skills/automate-github-issues
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.

Any agent
npx skills add google-labs-code/jules-skills --skill automate-github-issues
Clone the repo
git clone --depth 1 https://github.com/google-labs-code/jules-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for automate-github-issues

README.md
[![agentmods](https://agentmods.dev/badge/skills/google-labs-code/jules-skills/automate-github-issues/github.svg)](https://agentmods.dev/skills/google-labs-code/jules-skills/automate-github-issues)
Your own site
<a href="https://agentmods.dev/skills/google-labs-code/jules-skills/automate-github-issues"><img src="https://agentmods.dev/badge/skills/google-labs-code/jules-skills/automate-github-issues/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.

agentmods 80×15 button for automate-github-issues

Your own site · 80×15
<a href="https://agentmods.dev/skills/google-labs-code/jules-skills/automate-github-issues"><img src="https://agentmods.dev/badge/skills/google-labs-code/jules-skills/automate-github-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 982 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket warn 14 Sept 2026
  • Snyk warn 14 Sept 2026
How audits are shown
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.1 $0.00022 $0.00982
Opus 5.5 $0.00009 $0.00393
Sonnet 5.5 $0.00004 $0.00196
Haiku 4.5 $0.00002 $0.00098

Measured 1mo ago against content hash f738bf840dbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

automate-github-issues scanned grade C with 2 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.

The scan reads SKILL.md. This mod also ships 12 executable files (scripts/fleet-analyze.ts, scripts/fleet-dispatch.ts, scripts/fleet-merge.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- **Bun not found**: Install Bun: `curl -fsSL https://bun.sh/install | bash`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **Bun not found**: Install Bun: `curl -fsSL https://bun.sh/install | bash`
skills/automate-github-issues/SKILL.md · 137 lines

How it starts

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

Automate GitHub Issues with Jules

You are setting up a repository to automatically analyze open GitHub issues, plan implementation tasks, and dispatch parallel Jules coding agents to fix them.

What You're Setting Up

A 5-phase automated pipeline that runs via GitHub Actions (or locally):

  1. Analyze — Fetch open issues and format as structured markdown
  2. Plan — A Jules session performs deep code-level triage and produces self-contained task prompts
  3. Validate — Verify no two tasks modify the same file (prevents merge conflicts)
  4. Dispatch — Spawn parallel Jules sessions, one per task
  5. Merge — Sequential PR merge with CI validation

Setup Steps

Step 1: Copy fleet scripts to the repository

Copy the entire scripts/ directory from this skill into the target repository at scripts/fleet/:

Target structure:
scripts/fleet/
├── fleet-analyze.ts
├── fleet-plan.ts
├── fleet-dispatch.ts
├── fleet-merge.ts
├── types.ts
├── prompts/
│   ├── analyze-issues.ts
│   └── bootstrap.ts
└── github/
    ├── git.ts
    ├── issues.ts
    ├── markdown.ts
    └── cache-plugin.ts

Important: Preserve the directory structure exactly. The scripts use relative imports between files.

Step 2: Copy workflow templates

Copy the workflow files from assets/ to the repository's .github/workflows/ directory:

  • assets/fleet-dispatch.yml → .github/workflows/fleet-dispatch.yml
  • assets/fleet-merge.yml → .github/workflows/fleet-merge.yml

Step 3: Create a package.json for the fleet scripts

Create scripts/fleet/package.json with the required dependencies:

{
  "name": "fleet-scripts",
  "private": true,
  "type": "module",
  "dependencies": {
    "@google/jules-sdk": "^0.1.0",
    "octokit": "^4.1.0",
    "find-up": "^7.0.0"
  },
  "devDependencies": {
    "@types/bun": "^1.2.0"
  }
}

Step 4: Create environment template

Copy assets/.env.example to the repository root.

Step 5: Install dependencies

cd scripts/fleet && bun install

Read the full file on GitHub · 137 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. 1mo ago First seen · 137 lines · 22 tokens per session scan C f738bf840dbe

Subscribe to this mod's changes

automate-github-issues is a skill published in the GitHub repository google-labs-code/jules-skills (99 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 982 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

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.

aeonfun/aeon · 46 tokens

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…

nimbalyst/nimbalyst · 101 tokens

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)…

vybestack/llxprt-code · 88 tokens

cuga-github-issues

Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…

cuga-project/cuga-agent · 88 tokens

implement-issue

Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.

CopilotKit/OpenTag · 35 tokens