Borrowing it
Nothing to install: this file belongs to tomdwipo/claude-soul. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tomdwipo/claude-soul/main/.claude/commands/create-jira-task.mdgit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote 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.
[](https://agentmods.dev/commands/tomdwipo/claude-soul/create-jira-task)<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/create-jira-task"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/create-jira-task.svg" alt="Measured on agentmods" height="20"></a>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.02372 |
| Opus 5 | $0.00000 | $0.01186 |
| Sonnet 5 | $0.00000 | $0.00474 |
| Haiku 4.5 | $0.00000 | $0.00237 |
Grade A, and why
create-jira-task 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Jira Task Command
Create a Jira task ticket in the <PROJECT_KEY> project for: $ARGUMENTS
Instructions
-
Parse the arguments to extract:
- Summary: Short task title (prefix with
fix:,feat:,refactor:,test:,docs:as appropriate) - Description: Detailed description (if provided)
- Story Points: Numeric value (default: 2 if not specified)
- Choose Appendix (v3): Benchmark IDs (if provided, e.g. "AN-1, AN-9")
- Sprint:
active(default — adds to the currently running sprint),backlog(skip sprint assignment), or an explicit sprint id
- Summary: Short task title (prefix with
-
If arguments are unclear, ask the user for clarification before creating.
-
Create the ticket using the Jira MCP tools with these EXACT field mappings:
Field Mapping (DO NOT SEARCH — use these directly)
| Field | API Field | Type | Required |
|---|---|---|---|
| Project | <PROJECT_KEY> |
projectKey | Yes |
| Issue Type | Task |
issueTypeName | Yes |
| Assignee | <caller_account_id> (runtime lookup via mcp__atlassian__atlassianUserInfo — never hardcode another engineer's id) |
assignee_account_id | Yes |
| Story Points (UI) | customfield_<story_points_ui> |
number | Yes |
| Story point estimate | customfield_<story_point_estimate> |
number | Yes (same value as Story Points) |
| Choose Appendix (v3) | customfield_<appendix> |
multi-select array of {id} |
Required (never empty) — default [{id: "<id>"}] (AN-1 Low) if uncertain |
| Story Points Type | customfield_<sp_type> |
select | Optional |
| Story Point Type (v2) | customfield_<sp_type_v2> |
cascading select | Optional |
| Sprint | customfield_<sprint> |
number (sprint id) | Optional — note: the Sprint field id varies per Jira instance (often _10010 / _10020); discover yours via the Active Sprint Discovery step below, do not assume |
Active Sprint Discovery (use when sprint:active is requested)
The active sprint id changes every ~2 weeks, so look it up at runtime:
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.
- 8d ago First seen · 155 lines · 0 tokens per session scan A f31657d5f5b9
create-jira-task is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,372 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.