A read-only report for a run-tickets workflow run. It shows whether the run is still running or finished and reports each ticket's progress, timing, rework, conflicts, findings, and merges.

Use it to check the current or completed state of a ticket batch and see which tickets merged, need attention, or took the most time.

It gives one place to see what happened without inspecting agents or branches yourself. This makes blocked tickets, halted merges, and failed integration checks easier to find.

run-status — Skill for Claude Code by phobologic/claude_code

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 phobologic/claude_code_helpers --skill run-status

Clone the repo

git clone --depth 1 https://github.com/phobologic/claude_code_helpers

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/run-status/github.svg)](https://agentmods.dev/skills/phobologic/claude_code_helpers/run-status)

Your own site

<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/run-status"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/run-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/run-status"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/run-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 824 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.00092	$0.00824
Opus 5.5	$0.00037	$0.00330
Sonnet 5.5	$0.00018	$0.00165
Haiku 4.5	$0.00009	$0.00082

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

Security

Grade A, and why

run-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 5d 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/run-status/SKILL.md · 71 lines

How it starts

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

Run Status

Report on a /run-tickets run. The snapshot comes from run-tickets-status, which reads the run's own records: the run record /run-tickets writes into .worktrees/, the workflow journal of agent starts and typed results, and the final result once the run ends. Present what it says. Do not guess at state it does not report, and do not message or inspect agents yourself.

Steps

Run it from the repo the run belongs to:
```
run-tickets-status [<run-id>]
```
With no run ID it picks the newest run in the current repo, running or finished. Pass $ARGUMENTS through if the user named a run. If they ask about an earlier run without its ID ("yesterday's run", "the one before"), run run-tickets-status --list first and pick it from there.
If it exits with "no /run-tickets runs found", say there is no run to report in this repo.
Present the output. Lead with one line: state (running or finished), how many tickets merged out of the total, how long it has run or took, and anything needing attention (MERGES HALTED, BLOCKED, a failing integration check). Then the ticket list as the script printed it, including each ticket's time: and started: lines.

The started: line lists every agent the ticket ran, in order, with the local time it started and how long it took (running 3m for the one still going). A time from another day than the launch carries its date.

Timing notes, when they explain something:
- waiting is time a ticket spent between steps, mostly queued behind another ticket's merge.
- began Nm after launch means it waited on a dependency or a free worktree slot.
- A step that took several times longer than the same step on other tickets is worth pointing out.
- The closing "agent time by step" line shows where the run's time went.
Each ticket's effort: line lists every agent it ran, in order, with the effort it ran at and, once the run has finished, its token total (input included). It ends with the ticket's non-test lines changed, how many tickets depend on it, and on re-reviews how many previous findings the fix closed. Mention effort only when it explains something, such as a ticket whose reviews kept finding new problems.

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

5d ago Changed · +4 lines d8b68c586119
12d ago First seen · 67 lines · 92 tokens per session scan A 2f6a83828e03

Subscribe to this mod's changes

run-status is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 92 tokens to every session and 824 once invoked, about $0.0004 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-10-05.

Analytics and metrics Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

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

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens