agentmods.dev

workflow-identify

workflow-identify is a skill for Claude Code from fprochazka/claude-code-plugins. It costs 90 tokens per session (1,467 once invoked), scanned A, original, MIT.

A skill for discovering a project's issue tracker, team, ticket conventions, and workflow states before touching a ticket. It reads project instructions and repository documentation rather than assuming fixed names.

In plain words
What is it for?
It is for answering which workflow state to use and preparing the project-specific context before reading or changing a ticket.
Why use it?
It helps avoid moving tickets with the wrong team, tracker, or status, especially when projects use different workflow systems or rename their states.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Part of the teamwork plugin — 2 skills shipped together

not rated 15repo 7d ago A scan 90 tokens original MIT

Good fit It is for answering which workflow state to use and preparing the project-specific context before reading or changing a ticket.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fprochazka/claude-code-plugins/workflow-identify
View source ↗ fprochazka/claude-code-plugins
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 fprochazka/claude-code-plugins --skill workflow-identify
Clone the repo
git clone --depth 1 https://github.com/fprochazka/claude-code-plugins

Made for: Claude Code.

Or install teamwork, the plugin that ships this one along with the rest of its 2 skills.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fprochazka/claude-code-plugins/workflow-identify"><img src="https://agentmods.dev/badge/skills/fprochazka/claude-code-plugins/workflow-identify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,467 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.00090 $0.01467
Opus 5.5 $0.00036 $0.00587
Sonnet 5.5 $0.00018 $0.00293
Haiku 4.5 $0.00009 $0.00147

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

Security

Grade A, and why

workflow-identify 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 25d 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/teamwork/skills/workflow-identify/SKILL.md · 86 lines

How it starts

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

workflow-identify

Ground the agent in the project's issue tracker, team and workflow states before any command reads or moves a ticket. Every value is discovered at run time. This skill hardcodes no team name, no team id and no status name — a skill that carries them turns stale the day someone renames a state.

The output is the block in "Output contract" below. Print it, and the calling command carries it for the rest of the run.

Source order

The order is fixed. Do not skip ahead.

  1. Context already loaded. CLAUDE.md, AGENTS.md, everything they pull in through @ includes, and any memory already in context. These are free to read and they are the place a team writes its own conventions down. Search the context you already hold first — a CLAUDE.md that is a single @README.md line answers nothing on disk while its included content sits in your context. Grep the files on disk as a supplement, and follow every @ include you find:

    grep -rniE 'linear|jira|gitlab issue|github issue|team (key|id)|status|workflow|ticket|branch nam|^@' CLAUDE.md AGENTS.md 2>/dev/null | head -30

  2. The repo README.md. Many repos repeat the tracker facts there.

  3. The tracker API — last resort, and never silent. See "Stop before the API".

Stop before the API

If sources 1 and 2 do not answer, stop and tell the user what is missing. Do not go fishing through the API on your own. An API answer that lands nowhere is discovered again on every future run.

Offer two ways to persist the answer, and name the concrete file for each:

  • An edit to one of the loaded convention files — say which one, for example ./AGENTS.md or ./CLAUDE.md.
  • A Claude memory.

The user picks. Then query the tracker API, write the result into the chosen place, and continue. The next run reads it from source 1.

What to extract

  • Tracker — Linear, Jira, GitLab issues, GitHub issues, or none.
  • Team — display name, key, and id where the tracker has one. These are three different strings for one team. Never derive one from another.
  • Ticket ID pattern — TEAM-123, #123, or a tracker URL. The commands parse branch names and MR titles with it. A command takes the ticket of the work at hand from the MR title, the branch name, or the MR description, in that order, using this pattern; several MRs of one change usually share one ticket, and a command that finds none reports none rather than guessing.
  • Branch convention — the documented pattern if there is one, for example <initials>/<TICKET>-<slug>. Report none when nothing documents it, and do not invent one from the branches that happen to exist.
  • Workflow states — see below.

Read the full file on GitHub · 86 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. 25d ago First seen · 86 lines · 90 tokens per session scan A 58e5fb29c4be

Subscribe to this mod's changes

workflow-identify is a skill published in the GitHub repository fprochazka/claude-code-plugins (15 stars, last pushed 7d ago), licensed MIT. It adds 90 tokens to every session and 1,467 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-09-22.

Project management
Related

Other skills, from other repositories

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