issue-status

issue-status is a command for Claude Code from sjungling/sjungling-claude-plugins. It costs 12 tokens per session (1,100 once invoked), scanned A, original, MIT.

A command for moving a GitHub issue to a status column on project board 8. GitHub project boards organize issues into stages such as Backlog or Done.

In plain words
What is it for?
Use it to identify an issue by repository and number, then move it to a chosen board column such as In Progress or Done.
Why use it?
It avoids updating the wrong issue when the same issue number appears in more than one repository.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the workflow plugin — 10 commands, 1 agent shipped together

Good fit Use it to identify an issue by repository and number, then move it to a chosen board column such as In Progress or Done.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sjungling/sjungling-claude-plugins/issue-status
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.

Clone the repo
git clone --depth 1 https://github.com/sjungling/sjungling-claude-plugins

Made for: Claude Code.

Or install workflow, the plugin that ships this one along with the rest of its 10 commands, 1 agent.

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-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/issue-status/github.svg)](https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/issue-status)
Your own site
<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/issue-status"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/issue-status/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 issue-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/issue-status"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/issue-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,100 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01100
Opus 5 $0.00006 $0.00550
Sonnet 5 $0.00002 $0.00220
Haiku 4.5 $0.00001 $0.00110

Measured 9d ago against content hash 3fe961ef00d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

issue-status 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 9d 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.

plugins/workflow/commands/issue-status.md · 97 lines

How it starts

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

Move an issue to a column on project board 8 (https://github.com/orgs/moderneinc/projects/8).

Project 8 spans several repos (moderne-saas, codegenomeproject, …), so an issue number is not unique on the board — the same number exists in multiple repos. Resolve by repository, never by number alone.

Parse $ARGUMENTS:

  • First token = issue number (required).
  • A token containing / (e.g. moderneinc/codegenomeproject) = repository (optional). A bare repo without an owner is assumed under moderneinc.
  • Remaining tokens = target column name (optional, default In Progress). Match case-insensitively against the known columns below.

Known IDs (stable)

These are fixed for moderneinc project 8 — no need to re-resolve them:

  • PROJECT_ID = PVT_kwDOBBZwVM0q6g
  • FIELD_ID (Status) = PVTSSF_lADOBBZwVM0q6s4AATqk
  • Status option IDs:
    • Icebox = 6f4ce84a
    • Refine = e2a82074
    • Backlog = f75ad846
    • In Progress = 47fc9ee4
    • Ready to Communicate = 98236657
    • Done = 04d30f6f

If the requested column is not in this list, list the valid columns and stop.

Run

Resolve the per-issue item ID scoped to its repository, then set the Status field. Replace <ISSUE> with the issue number, <OPTION_ID> with the option ID for the requested column, and <REPO> with owner/repo (empty if the caller gave none):

ISSUE=<ISSUE>
OPTION_ID=<OPTION_ID>
REPO=<REPO>   # e.g. moderneinc/codegenomeproject; empty if not specified

ITEMS=$(gh project item-list 8 --owner moderneinc --format json --limit 1000)

if [ -n "$REPO" ]; then
  # .content.repository is "owner/repo" — the reliable disambiguator.
  # Here-strings (<<<), not `echo "$ITEMS" | …`: zsh's echo mangles the \n/\t
  # escapes inside issue titles and corrupts the JSON.
  ITEM_ID=$(jq -r --arg n "$ISSUE" --arg r "$REPO" \
    '.items[] | select(.content.number == ($n|tonumber) and .content.repository == $r) | .id' <<<"$ITEMS")
else
  MATCHES=$(jq --arg n "$ISSUE" \
    '[.items[] | select(.content.number == ($n|tonumber))]' <<<"$ITEMS")
  if [ "$(jq 'length' <<<"$MATCHES")" -gt 1 ]; then
    echo "Issue #$ISSUE is ambiguous — it exists in multiple repos on project 8:"
    jq -r '.[] | "  \(.content.repository) — \(.content.title)"' <<<"$MATCHES"
    echo "Re-run with the repo, e.g.: /workflow:issue-status $ISSUE <column> moderneinc/<repo>"
    exit 1
  fi
  ITEM_ID=$(jq -r '.[0].id // empty' <<<"$MATCHES")
fi

if [ -z "$ITEM_ID" ]; then
  TARGET="${REPO:-moderneinc/<repo>}"
  echo "Issue #$ISSUE${REPO:+ in $REPO} is not on project 8. Add it first with:"
  echo "  gh project item-add 8 --owner moderneinc --url https://github.com/$TARGET/issues/$ISSUE"
  exit 1
fi

gh project item-edit \
  --id "$ITEM_ID" \
  --project-id "PVT_kwDOBBZwVM0q6g" \
  --field-id "PVTSSF_lADOBBZwVM0q6s4AATqk" \
  --single-select-option-id "$OPTION_ID"

Read the full file on GitHub · 97 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. 9d ago First seen · 97 lines · 12 tokens per session scan A 3fe961ef00d6

Subscribe to this mod's changes

issue-status is a command published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 25d ago), licensed MIT. It adds 12 tokens to every session and 1,100 once invoked, about $0.0001 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-30.