issue-progress-tracking

issue-progress-tracking is a skill for Claude Code, Codex from yonatangross/orchestkit. It costs 73 tokens per session (1,118 once invoked), scanned A, original, MIT.

A workflow for tracking software work through GitHub issues from start to pull request. It uses labels, feature branches, small commits, progress comments, and links between issues and pull requests.

In plain words
What is it for?
Use it when starting work on an issue, creating an issue-specific branch, recording progress, making issue-referenced commits, or linking a pull request that closes the issue.
Why use it?
It keeps the issue record synchronized with development progress and makes the work easier to follow from planning through completion.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the ork plugin — 68 skills, 35 commands, 36 agents, 32 hooks shipped together

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/yonatangross/orchestkit/issue-progress-tracking
Any agent
npx skills add yonatangross/orchestkit --skill issue-progress-tracking
Clone the repo
git clone --depth 1 https://github.com/yonatangross/orchestkit

Made for: Claude Code, Codex.

Or install ork, the plugin that ships this one along with the rest of its 68 skills, 35 commands, 36 agents, 32 hooks.

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 issue-progress-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/yonatangross/orchestkit/issue-progress-tracking.svg)](https://agentmods.dev/skills/yonatangross/orchestkit/issue-progress-tracking)
Your own site
<a href="https://agentmods.dev/skills/yonatangross/orchestkit/issue-progress-tracking"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/issue-progress-tracking.svg" alt="Measured on agentmods" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,118 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00073 $0.01118
Opus 5 $0.00036 $0.00559
Sonnet 5 $0.00015 $0.00224
Haiku 4.5 $0.00007 $0.00112

Measured yesterday against content hash a3955bc34cae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issue-progress-tracking 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 yesterday.

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.

plugins/ork/skills/issue-progress-tracking/SKILL.md · 155 lines

How it starts

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

Issue Progress Tracking

Ceremony guide for tracking GitHub issue progress via gh CLI. Ensures issues stay updated as work progresses from start to PR.

Invocation

This skill is user-invocable: false and disable-model-invocation: true: there is no /ork: form and the model cannot auto-select it (#3313). An agent loads it explicitly by Reading this file's path:

${CLAUDE_PLUGIN_ROOT}/skills/issue-progress-tracking/SKILL.md

Phase 1: Start Work

Label the issue and create a feature branch:

# Move issue to in-progress
gh issue edit $ARGUMENTS[0] --add-label "status:in-progress" --remove-label "status:todo"
gh issue comment $ARGUMENTS[0] --body "Starting work on this issue."

# Create feature branch
git checkout -b issue/$ARGUMENTS[0]-brief-description

Rules:

  • Always branch from the default branch (main/dev)
  • Branch name format: issue/<number>-<brief-description>
  • Never work directly on main/dev

Phase 2: During Work — Small Commits

Commit after each logical step, not at the end. Every commit references the issue:

# Each commit references the issue number
git commit -m "feat(#$ARGUMENTS[0]): add user model

Co-Authored-By: Claude <[email protected]>"

Rules:

  • One logical change per commit (atomic)
  • Reference issue in every commit: type(#N): description
  • Commit early and often — don't accumulate a massive diff

Phase 3: Report Progress (Long Implementations)

For multi-step work, post progress updates:

gh issue comment $ARGUMENTS[0] --body "Progress update:
- Completed: database schema, API endpoints
- In progress: frontend components
- Remaining: tests, documentation"

When to post updates:

  • After completing a major milestone
  • When blocked or changing approach
  • Before stepping away from a long task

Phase 4: Complete Work

Create the PR and update labels:

# Create PR that closes the issue
gh pr create \
  --title "feat(#$ARGUMENTS[0]): brief description" \
  --body "Closes #$ARGUMENTS[0]

## Changes
- Change 1
- Change 2

## Test Plan
- [ ] Unit tests pass
- [ ] Manual verification"

# Update issue status
gh issue edit $ARGUMENTS[0] --add-label "status:in-review" --remove-label "status:in-progress"

Read the full file on GitHub · 155 lines

Files

What ships with it

4 files 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.

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. yesterday First seen · 155 lines · 73 tokens per session scan A a3955bc34cae

Subscribe to this mod's changes

issue-progress-tracking is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,118 once invoked, about $0.0004 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-09-03.