work

work is a skill for Claude Code from quay/ai-helpers. It costs 49 tokens per session (1,282 once invoked), scanned A, original, MIT.

A continuous workflow for taking one JIRA ticket from assignment through a merge-ready pull request. JIRA is a system for tracking software work, and the workflow records progress in a state file on each loop.

In plain words
What is it for?
Use it to assign, implement, test, review, and monitor a single ticket until completion, with an optional manual stepping mode.
Why use it?
It keeps the ticket process in one state machine instead of requiring separate start, coding, pull-request, and polling steps.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions AGENTS.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Bash(bash .claude/scripts/tick-state.sh *).

Part of the dev plugin — 16 skills, 1 command shipped together

Good fit Use it to assign, implement, test, review, and monitor a single ticket…

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/quay/ai-helpers
agentmods
npx agentmods add skills/quay/ai-helpers/work

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 16 skills, 1 command.

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 work

README.md
[![agentmods](https://agentmods.dev/badge/skills/quay/ai-helpers/work.svg)](https://agentmods.dev/skills/quay/ai-helpers/work)
Your own site
<a href="https://agentmods.dev/skills/quay/ai-helpers/work"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/work.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,282 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.00049 $0.01282
Opus 5 $0.00024 $0.00641
Sonnet 5 $0.00010 $0.00256
Haiku 4.5 $0.00005 $0.00128

Measured yesterday against content hash 05cd34024328, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

work 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/dev/skills/work/SKILL.md · 161 lines

How it starts

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

Ralph Loop — Single-Ticket Workflow

Implement JIRA ticket $ARGUMENTS from assignment to merge-ready PR in one continuous loop.

Parse $ARGUMENTS: first token is the ticket key, --manual (if present) sets manual stepping mode.

Initialize

bash .claude/scripts/tick-state.sh init $TICKET --mode $MODE

The Tick Loop

while state != COMPLETE:
    1. READ   — bash .claude/scripts/tick-state.sh read $TICKET
    2. ACT    — execute the handler for the current state
    3. WRITE  — bash .claude/scripts/tick-state.sh advance $TICKET <NEXT_STATE>
    4. SLEEP  — if DORMANT: the poll script blocks (0 tokens consumed)
    5. PAUSE  — if manual mode: ask user [c]ontinue / [s]kip / [i]nspect / [a]bort
    6. LOOP   — go back to step 1

CRITICAL: Do NOT stop between ticks. The only valid exit points are:

  • State reaches COMPLETE
  • Manual mode and user chooses [a]bort
  • triage_attempts >= 3 (ask user for guidance)

State Handlers

ASSIGN

View the JIRA ticket, assign it, transition to ASSIGNED.

bash .claude/scripts/jira-ops.sh view $TICKET
bash .claude/scripts/jira-ops.sh assign $TICKET
bash .claude/scripts/jira-ops.sh transition $TICKET "ASSIGNED"

-> advance to BRANCH

BRANCH

Check backport requirement, create feature branch, load area docs.

bash .claude/scripts/jira-ops.sh check-version $TICKET
git checkout ${PRIMARY_BRANCH:-master} && git pull origin ${PRIMARY_BRANCH:-master}
git checkout -b $TICKET-short-description
bash .claude/scripts/tick-state.sh set $TICKET branch "<branch-name>"

-> advance to IMPLEMENT

IMPLEMENT

Read AGENTS.md plus area docs. Write code, create tests, handle edge cases. -> advance to TEST

TEST

Run quality checks and tests:

bash .claude/scripts/format-and-lint.sh

If tests fail: fix and re-run. Stay in TEST until all pass. -> advance to COMMIT

COMMIT

Stage and commit:

git add <specific files>
git commit -m "<subsystem>: <what changed> ($TICKET)"

If pre-commit hooks fail: fix, re-stage, new commit. Stay in COMMIT until success. -> advance to PR_CREATE

Read the full file on GitHub · 161 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. yesterday First seen · 161 lines · 49 tokens per session scan A 05cd34024328

Subscribe to this mod's changes

work is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 49 tokens to every session and 1,282 once invoked, about $0.0002 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-04.