A skill for launching ticketmill, a batch process that takes selected GitHub issues through planning, coding, testing, review, and pull-request creation.

Use it to process a group of GitHub issues end to end, including research, implementation, quality checks, pull-request creation, and squash-merging into an integration branch.

It organizes many issue implementations into one logged and resumable run while leaving the final batch pull request for human review.

mill — Skill for Claude Code by aaddrick/ticketmill

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add aaddrick/ticketmill

Claude Code

/plugin install ticketmill

Made for: Claude Code.

Or install ticketmill, the plugin that ships this one along with the rest of its 4 skills, 5 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aaddrick/ticketmill/mill/github.svg)](https://agentmods.dev/skills/aaddrick/ticketmill/mill)

Your own site

<a href="https://agentmods.dev/skills/aaddrick/ticketmill/mill"><img src="https://agentmods.dev/badge/skills/aaddrick/ticketmill/mill/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aaddrick/ticketmill/mill"><img src="https://agentmods.dev/badge/skills/aaddrick/ticketmill/mill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,682 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00062	$0.03682
Opus 5.5	$0.00025	$0.01473
Sonnet 5.5	$0.00012	$0.00736
Haiku 4.5	$0.00006	$0.00368

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

Security

Grade A, and why

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

skills/mill/SKILL.md · 254 lines

How it starts

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

mill: launch a ticketmill batch run

Runs the ticketmill engine. For each selected GitHub issue: research, contrarian-gated approach and plan, per-task implementation with quality loops, a test loop, PR creation, spec + code review loops, and a squash-merge into a batch integration branch. The run ends with ONE batch PR for a human to review and merge; the engine never merges to the base branch itself.

Hard preconditions: check these IN ORDER before doing anything else

The Workflow tool must be available in this session. Check your available tools for a tool named Workflow that accepts a scriptPath input. If it is not available: STOP IMMEDIATELY. Tell the user:

The ticketmill engine requires the Claude Code Workflow tool, which is not available in this session/plan. The engine cannot run without it.

NEVER attempt to simulate, approximate, or hand-execute the batch pipeline yourself (no ad-hoc issue implementing, no manual worktree orchestration in place of the engine). The engine's value is its journaling, claims, circuit breakers, and resumability. An inline imitation has none of those and is strictly worse than not running at all.
The target repo must have a profile at <repo-root>/.claude/ticketmill.json. If missing, stop and direct the user to run /ticketmill:mill-init first. Do not write a profile ad hoc: mill-init exists to verify the environment (doctor pass) before a profile is trusted.
Locate the engine script, in this order:
1. ${CLAUDE_PLUGIN_ROOT}/workflows/ticketmill.js (plugin install)
2. <repo-root>/.claude/workflows/ticketmill.js (copied by mill-init)
If neither exists, stop and direct the user to /ticketmill:mill-init.

Engine-owned paths need a clean root tree

If an issue's fix touches the ticketmill profile (.claude/ticketmill.json), the agent roster (.claude/agents/**), or the engine copy (.claude/workflows/ticketmill.js, .claude/scripts/ticketmill/**), check the root working tree before you launch. The engine works from each issue's own worktree, and that worktree only sees committed state. Uncommitted edits sitting in the root tree, like a freshly forged agent or a profile field you just added, are invisible to it.

Read the full file on GitHub · 254 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.

1mo ago First seen · 254 lines · 62 tokens per session scan A 95c6b333ff13

Subscribe to this mod's changes

mill is a skill published in the GitHub repository aaddrick/ticketmill (16 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 3,682 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-30.

Git and workflow Project management

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