What is JIRA-THIS-BRANCH?

A command for creating a Jira ticket from the code changes unique to the current Git branch and linking that ticket to the branch. Jira is a system teams use to track software work.

Reviewing branch changes, drafting and creating a Jira ticket, linking it to the branch, setting it to In Progress, and assigning it to the user.

It connects a branch’s changes with a work item so the reason for the code is easier to track. It requires a team name and parent ticket before creating the ticket.

How dep/agent-rules configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to dep/agent-rules. 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/dep/agent-rules/main/.agents/commands/JIRA-THIS-BRANCH.md

Clone the repo

git clone --depth 1 https://github.com/dep/agent-rules

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/dep/agent-rules/jira-this-branch/github.svg)](https://agentmods.dev/commands/dep/agent-rules/jira-this-branch)

Your own site

<a href="https://agentmods.dev/commands/dep/agent-rules/jira-this-branch"><img src="https://agentmods.dev/badge/commands/dep/agent-rules/jira-this-branch/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/dep/agent-rules/jira-this-branch"><img src="https://agentmods.dev/badge/commands/dep/agent-rules/jira-this-branch.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 153 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00153
Opus 5.5	$0.00000	$0.00061
Sonnet 5.5	$0.00000	$0.00031
Haiku 4.5	$0.00000	$0.00015

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

Security

Grade A, and why

JIRA-THIS-BRANCH 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 1mo 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.

.agents/commands/JIRA-THIS-BRANCH.md · 21 lines

What it actually says

JIRA-THIS-BRANCH v1.0.0

Create a Jira ticket using the Atlassian skill based on the current branch's unique code changes, then link the ticket to the branch.

REQUIRED INFORMATION:

Team name (ask if not provided)
Parent ticket ID (ask if not provided)

STEPS:

Analyze code changes unique to this branch
Generate appropriate Jira ticket with:
- Title summarizing the changes
- Description detailing the modifications
Create the ticket in Jira
Link the ticket to the branch
Set ticket status to "In Progress"
Assign ticket to the user

OUTPUT:

Provide the created ticket ID and confirmation of all actions completed.

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.

1mo ago First seen · 21 lines · 0 tokens per session scan A 8593341579b7

Subscribe to this mod's changes

JIRA-THIS-BRANCH is a command published in the GitHub repository dep/agent-rules (11 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 153 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.

Git and workflow Project management ai-agents

agent-rules: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

JIRA-THIS-BRANCH v1.0.0

REQUIRED INFORMATION:

STEPS:

OUTPUT:

What this file has done since we first saw it

Other commands, from other repositories

project

land

standup

repo-architect

sync

claim