claude-em: Skill for Claude Code

.claude/skills/jira/SKILL.md

jira is a skill for Claude Code from jcesarperez/claude-em. It costs 129 tokens per session (2,369 once invoked), scanned A, original, MIT.

A general guide for working with Jira, a system for tracking projects and issues such as bugs, tasks, stories, and epics.

In plain words
What is it for?
Use it to create, find, or update Jira issues, including bugs, tasks, stories, sub-tasks, and epics.
Why use it?
It explains how to handle common Jira requests while checking that the project configuration is present.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is jcesarperez/claude-em's own configuration. It tells Claude Code how to work on claude-em 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 claude-em configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jcesarperez/claude-em. 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/jcesarperez/claude-em/main/.claude/skills/jira/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jcesarperez/claude-em

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 jira

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jcesarperez/claude-em/jira"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 129 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,369 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.00129 $0.02369
Opus 5 $0.00064 $0.01184
Sonnet 5 $0.00026 $0.00474
Haiku 4.5 $0.00013 $0.00237

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

Security

Grade A, and why

jira 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/skills/jira/SKILL.md · 215 lines

How it starts

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

Skill: Jira — Project

Manual Setup

Before using this skill, replace the following placeholders throughout this file — including the name: and description: in the frontmatter above:

  • name: → use a short identifier for your project (e.g. jira-platform, jira-core)
  • description: → update "any Jira project" to mention your actual project name, so Claude picks the right skill when you have multiple

Then replace the configuration placeholders:

Placeholder Description How to find it
{{PROJECT_KEY}} Your Jira project key Visible in any issue key (e.g. PLAT-123 → key is PLAT)
{{CLOUD_ID}} Your Atlassian Cloud ID Run jira config list or extract from your Atlassian URL
{{BASE_URL}} Your Jira domain e.g. yourcompany.atlassian.net

Delete this section and the "Auto-detection" section below once you've replaced the placeholders.


Auto-detection (always run this first)

Before doing anything else, check if any placeholder is still unconfigured:

  • If {{PROJECT_KEY}} appears literally in this file → ask: "What is your Jira project key? (e.g. PLAT, ENG, CORE)"
  • If {{CLOUD_ID}} appears literally in this file → ask: "What is your Atlassian Cloud ID? You can find it by running jira config list or from your Atlassian admin URL."
  • If {{BASE_URL}} appears literally in this file → ask: "What is your Jira domain? (e.g. yourcompany.atlassian.net)"

Once the user provides the values, use them for the rest of the conversation without asking again.

Then ask: "Should I save these values in the skill so you don't have to enter them again in future conversations?"

  • If yes → edit this SKILL.md file, replacing each {{PLACEHOLDER}} with the value the user provided, and confirm when done.
  • If no → keep them only for this conversation.

Configuration

Field Value
Project {{PROJECT_KEY}}
cloudId {{CLOUD_ID}}
Base URL {{BASE_URL}}
Assignee None (unless user specifies)
Reporter Current user
Priority Medium (unless user specifies)
Components None by default
Labels None by default

Read the full file on GitHub · 215 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 · 215 lines · 129 tokens per session scan A 1d8f93e1de14

Subscribe to this mod's changes

jira is a skill published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 2mo ago), licensed MIT. It adds 129 tokens to every session and 2,369 once invoked, about $0.0006 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-08-30.

Related

Other skills, from other repositories

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

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

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

me2resh/apexyard · 24 tokens