workflow

workflow is a skill for Claude Code from JustinThomas2/agentrc. It costs 30 tokens per session (587 once invoked), scanned A, original, MIT.

A read-only status checker for an issue-to-pull-request workflow. It shows the expected stages and checks the current Git branch and pull-request status using local Git and GitHub information.

In plain words
What is it for?
Use it to inspect the current branch, whether it has uncommitted or unsynchronised changes, and whether an associated pull request exists or needs review.
Why use it?
It lets you see where work currently stands without changing files, branches, commits, or GitHub data. It also explains what each workflow stage is supposed to do.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Good fit Use it to inspect the current branch, whether it has uncommitted or unsynchronised changes, and whether an associated pull request exists or needs review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/justinthomas2/agentrc/workflow
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 JustinThomas2/agentrc --skill workflow
Clone the repo
git clone --depth 1 https://github.com/JustinThomas2/agentrc

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 workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/justinthomas2/agentrc/workflow/github.svg)](https://agentmods.dev/skills/justinthomas2/agentrc/workflow)
Your own site
<a href="https://agentmods.dev/skills/justinthomas2/agentrc/workflow"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/workflow/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 workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/justinthomas2/agentrc/workflow"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 587 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.00030 $0.00587
Opus 5.5 $0.00012 $0.00235
Sonnet 5.5 $0.00006 $0.00117
Haiku 4.5 $0.00003 $0.00059

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

Security

Grade A, and why

workflow 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 2mo 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/workflow/SKILL.md · 58 lines

How it starts

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

Your task

This skill is read-only. Run only:

  • git status -sb
  • gh pr status

Do not branch, commit, push, post comments, edit files, or run mutating GitHub commands.

Pipeline Map

Print this compact map first, one line per skill:

  • file-issue: rough idea -> GitHub issue draft or filed issue; stops before filing for approval.
  • work-issue: issue number -> local branch with committed implementation; stops before push or PR.
  • open-pr: issue number -> pushed branch and opened PR; stops after reporting the PR URL.
  • review-pr: PR number -> posted review feedback comment; stops before posting for approval.
  • address-feedback: PR number -> committed review fixes; stops before push or reviewer replies.
  • respond-feedback: PR number -> posted approved reviewer replies; ends the workflow.

State Detection

Use git status -sb to identify:

  • current branch
  • whether the branch is ahead of, behind, or diverged from its upstream
  • whether there are uncommitted changes

Use gh pr status to identify:

  • whether the current branch already has a PR
  • the PR number when present
  • whether the visible review decision is approved, changes requested, or review required

Then print:

  • You are here: one concise sentence describing the current state.
  • Next: the exact next skill invocation.

Choose the next invocation this way:

  • On main with no feature branch context: file-issue with the rough idea.
  • On a non-main branch with uncommitted changes: finish or discard the local changes before invoking another pipeline skill.
  • On a non-main branch with commits ahead of main and no PR: open-pr with issue N. Infer N from a branch segment like 16 in refactor/16-workflow-skill-names; if no issue number is clear, say that the issue number is needed.
  • On a branch with an open PR and no review decision yet: review-pr with PR N to review it, or wait for an external review.
  • On a branch with an open PR and changes requested: address-feedback with PR N.
  • After review-fix commits are ready on a PR branch: respond-feedback with PR N once the fixes have been pushed and reviewed by Justin.
  • If the state is ambiguous, say what is missing instead of guessing.

Read the full file on GitHub · 58 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. 2mo ago First seen · 58 lines · 30 tokens per session scan A 2aa4507289dc

Subscribe to this mod's changes

workflow is a skill published in the GitHub repository JustinThomas2/agentrc (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 587 once invoked, about $0.0001 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-31.