agentmods.dev

borderlint: Command for Claude Code

.claude/commands/task-jira.md

task-jira is a command for Claude Code from iolairus/borderlint. It costs 13 tokens per session (392 once invoked), scanned A, original, MIT.

A formatter that turns software tasks into Jira-ready markup. Jira is a project-tracking system used to manage issues and development work.

In plain words
What is it for?
Use it to export one task, all tasks, or tasks with a chosen status into backlog/exports/jira/ as Jira wiki-markup files.
Why use it?
It removes the repetitive work of converting task details and acceptance scenarios into Jira's description format while preserving traceability to the source files.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

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

not rated 10repo 7d ago A scan 13 tokens original MIT
View source ↗ iolairus/borderlint
Reuse

Borrowing it

Nothing to install: this file belongs to iolairus/borderlint. 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/iolairus/borderlint/main/.claude/commands/task-jira.md
Clone the repo
git clone --depth 1 https://github.com/iolairus/borderlint

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/iolairus/borderlint/task-jira"><img src="https://agentmods.dev/badge/commands/iolairus/borderlint/task-jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 392 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.00013 $0.00392
Opus 5.5 $0.00005 $0.00157
Sonnet 5.5 $0.00003 $0.00078
Haiku 4.5 $0.00001 $0.00039

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

Security

Grade A, and why

task-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 2mo 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/task-jira.md · 21 lines

What it actually says

Export the task $ARGUMENTS (a Jira key like PROJ-123, all, or a status like enriched) to Jira-compatible markup.

Steps

  1. Read workflow.yaml (jira.project_key, jira.export_dir, jira.default_issue_type). Resolve which tasks to export from the argument; default to all with status: enriched.

    Exports are written in English (the repo's only content language). If a task was written in another language, translate the full content to English, keeping Gherkin keywords (Given/When/Then) as-is.

  2. For each task render backlog/exports/jira/<id>.md in Jira wiki markup (not GitHub markdown):

    • h2. headings, *bold*, {code}...{code} blocks for Gherkin, ||header|| tables, # / * lists.
    • Structure: Summary line (<id> — <title>), issue type (jira.default_issue_type unless the task says otherwise), priority, h2. Goal, h2. Acceptance criteria with each scenario in a {code} block, h2. Notes, and a final line Source: backlog/tasks/<file> for traceability.
    • Do not include the YAML frontmatter.

  3. Print where the files were written and remind the user: paste into Jira's description field with the wiki editor, or bulk-import.

  4. Draft IDs: if any exported task has a draft ID (<project_key>-Dnn), remind the user to create the issue in Jira and then rename the task file and its id: frontmatter to the real key — offer to do the rename if they provide the keys now.

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. 2mo ago First seen · 21 lines · 13 tokens per session scan A bb2f9dd3afe9

Subscribe to this mod's changes

task-jira is a command published in the GitHub repository iolairus/borderlint (10 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 392 once invoked, about $0.0001 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-08-31.

Project management
Related

task-jira compared with commands from other repositories

task-jira next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
task-jiraiolairus/borderlintCommand107d agoMITA13Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code