recipe-skills: Command for Claude Code

.claude/commands/jira-recipes.md

jira-recipes is a command for Claude Code from workato-devs/recipe-skills. It costs 0 tokens per session (958 once invoked), scanned A, original, MIT.

A set of Jira instructions for creating Workato recipes. Jira is a service for tracking issues, projects, and software sprints.

In plain words
What is it for?
Searching with JQL, checking sprints, managing issues, comments, users, and attachments, retrieving issue details, and using HTTP for unsupported operations.
Why use it?
It supplies the Jira-specific operations, trigger choices, and exact action naming needed to generate valid recipes.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is workato-devs/recipe-skills's own configuration. It tells Claude Code how to work on recipe-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything recipe-skills configures →

Part of the recipe-skills plugin — 8 skills, 7 commands shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to workato-devs/recipe-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/workato-devs/recipe-skills/main/.claude/commands/jira-recipes.md
Clone the repo
git clone --depth 1 https://github.com/workato-devs/recipe-skills

Made for: Claude Code.

Or install recipe-skills, the plugin that ships this one along with the rest of its 8 skills, 7 commands.

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 jira-recipes

README.md
[![agentmods](https://agentmods.dev/badge/commands/workato-devs/recipe-skills/jira-recipes/github.svg)](https://agentmods.dev/commands/workato-devs/recipe-skills/jira-recipes)
Your own site
<a href="https://agentmods.dev/commands/workato-devs/recipe-skills/jira-recipes"><img src="https://agentmods.dev/badge/commands/workato-devs/recipe-skills/jira-recipes/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 jira-recipes

Your own site · 80×15
<a href="https://agentmods.dev/commands/workato-devs/recipe-skills/jira-recipes"><img src="https://agentmods.dev/badge/commands/workato-devs/recipe-skills/jira-recipes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 958 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.00000 $0.00958
Opus 5 $0.00000 $0.00479
Sonnet 5 $0.00000 $0.00192
Haiku 4.5 $0.00000 $0.00096

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

Security

Grade A, and why

jira-recipes 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 10d 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.

.claude/commands/jira-recipes.md · 105 lines

How it starts

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

Jira Recipes Skill

DEPENDENCY: Run /workato-recipes first if not already loaded. This skill requires the base Workato knowledge for triggers, control flow, datapills, and recipe structure.

You are now equipped with Jira-specific knowledge for writing Workato recipes. This skill extends the workato-recipes base skill and focuses on Jira-specific patterns.

Capabilities

With this skill loaded, you can:

  • Search Jira issues using JQL queries with dynamic filters
  • Query sprint status and issue breakdowns
  • Create and update Jira issues with full field support
  • Get issue details by ID or key
  • Manage comments, users, and attachments
  • Handle operations not covered by native actions via adhoc HTTP

Trigger Type Selection

Ask the user which trigger type they need:

  • API Endpoint (workato_api_platform) - External HTTP access
  • Callable Recipe (workato_recipe_function) - Internal recipe calls

See workato-recipes skill for trigger implementation details.

Jira-Specific Knowledge

Action Name Casing (CRITICAL)

search_issues_by_JQL is case-sensitive. The JQL portion MUST be uppercase. Using search_issues_by_jql or any other casing will fail with "Select an app and action" in the Workato UI.

jql Is a Connector Internal (CRITICAL)

The jql field is Jira's native parameter. It must NEVER appear in extended_input_schema. Set extended_input_schema: [] for search actions.

// CORRECT
"input": { "jql": "='project = \"ENG\"'" },
"extended_input_schema": []

// WRONG - causes duplicate field in UI
"input": { "jql": "='project = \"ENG\"'" },
"extended_input_schema": [{ "name": "jql", "type": "string" }]

Field Name: jql Not query

The native field name is jql, not query. Using query causes "Field not recognized."

JQL Formula Mode (CRITICAL)

JQL values use = formula mode with bare _dp() calls. No #{} interpolation. No outer parentheses.

"jql": "='project = \"' + _dp('{...project_key...}') + '\" AND sprint in openSprints()'"

Read the full file on GitHub · 105 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. 10d ago First seen · 105 lines · 0 tokens per session scan A 60d85e4ddbc2

Subscribe to this mod's changes

jira-recipes is a command published in the GitHub repository workato-devs/recipe-skills (18 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 958 tokens. 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.