agentmods.dev

jira-setup

jira-setup is a command for Claude Code from mumerfarooq-con/asdlc-tools. It costs 24 tokens per session (674 once invoked), scanned A, original, MIT.

A setup command for configuring Jira and Bitbucket access for the related Jira workflow. Jira tracks project work, while Bitbucket hosts source code and related development activity.

In plain words
What is it for?
Use it to initialise or check Jira settings, create missing access-rule and known-trap document templates, and verify Jira and Bitbucket test calls.
Why use it?
It creates the needed repository configuration, checks required environment variables, and tests access without putting secret token values in files.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the asdlc plugin — 5 commands, 15 agents shipped together

not rated 2repo 5d ago A scan 24 tokens original MIT

Good fit Use it to initialise or check Jira settings, create missing access-rule and known-trap document templates, and verify Jira and Bitbucket test calls.

Compare 6 commands from other repositories ↓
View source ↗ mumerfarooq-con/asdlc-tools
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add mumerfarooq-con/asdlc-tools
Claude Code
/plugin install asdlc

Made for: Claude Code.

Or install asdlc, the plugin that ships this one along with the rest of its 5 commands, 15 agents.

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-setup

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/mumerfarooq-con/asdlc-tools/jira-setup"><img src="https://agentmods.dev/badge/commands/mumerfarooq-con/asdlc-tools/jira-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 674 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.00024 $0.00674
Opus 5.5 $0.00010 $0.00270
Sonnet 5.5 $0.00005 $0.00135
Haiku 4.5 $0.00002 $0.00067

Measured 9d ago against content hash 03735f05f54e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jira-setup 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 9d 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.

plugins/asdlc/commands/jira-setup.md · 35 lines

What it actually says

/asdlc:jira-setup

Prepare this repo (run from its root) for /asdlc:jira-run. Scripts live in ${CLAUDE_PLUGIN_ROOT}/jira/scripts/; call them by that full path. Never print, echo or write a token value: tokens stay in env vars (JIRA_EMAIL, JIRA_TOKEN, BITBUCKET_TOKEN, and BITBUCKET_EMAIL with BB_AUTH=basic), never in a file.

  1. Config. Run ${CLAUDE_PLUGIN_ROOT}/jira/scripts/jira-setup.sh init $ARGUMENTS.
    • It writes .asdlc/jira.conf from the plugin template, pre-filling values from the env vars older in-repo setups used (JIRA_URL, JIRA_PROJECT, BITBUCKET_*...). An existing config is left alone unless --force was passed.
    • If it reports keys still empty, ask me for each value, then set them with Edit in .asdlc/jira.conf. Don't guess values.
  2. Docs. Run ${CLAUDE_PLUGIN_ROOT}/jira/scripts/jira-setup.sh docs. It creates the access-rules and known-traps files (paths from the config) from templates if they're missing. Filling them is a human task; don't add entries.
  3. Check. Run ${CLAUDE_PLUGIN_ROOT}/jira/scripts/jira-setup.sh check. It verifies the config, that the token env vars are set, makes one Jira and one Bitbucket test call, and checks every configured status exists in the project's workflow.
    • A FAIL about a value in the config: show me the line, ask for the right value, fix it, re-run.
    • A FAIL about an env var or auth: tell me which variable to set in my shell profile (e.g. export JIRA_TOKEN=... in ~/.zshrc), then STOP — you can't fix that for me.
    • warn lines: relay them; they don't block. A missing STATUS_NEEDS_INFO needs a Jira admin.
  4. Wrap up. Suggest adding these lines to .gitignore (plans and PRDs hold ticket text and must never be staged by a run): plans/.jira-run.lock, plans/*.plan.md, prds/. A warn from check about them means they're missing. Also suggest committing .asdlc/jira.conf plus the two docs files. Then show the final config (${CLAUDE_PLUGIN_ROOT}/jira/scripts/jira-conf.sh) and say the repo is ready for /asdlc:jira-run.
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. 9d ago First seen · 35 lines · 24 tokens per session scan A 03735f05f54e

Subscribe to this mod's changes

jira-setup is a command published in the GitHub repository mumerfarooq-con/asdlc-tools (2 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 674 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-10-09.

Claude CodeCode reviewMulti-AgentProject managementai-agentsclaude-code-pluginsdlc
Related

Other commands, from other repositories

poc

Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.

avelikiy/great_cto · 54 tokens

spec

Know the problem but not yet the product, the requirements or the design? Run it — you get, stage by stage, a discovery plan (/spec discover), a PRD (/spec prd) and a build spec: requirements.md + design.md + tasks.md (/spec or /spec build). Run before writing any code.

avelikiy/great_cto · 71 tokens

ownership

When you need to know who owns a path and who answers for it — the service ownership matrix (team, lead, on-call, SLA) auto-detected from git with CODEOWNERS generated, plus on-call rotations, shift handoffs and escalation paths.

avelikiy/great_cto · 52 tokens

rfc

RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.

avelikiy/great_cto · 24 tokens

exception

Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.

avelikiy/great_cto · 47 tokens

auto-task

Create an agent team for autonomous workflow: plan (Architect teammate + PM teammate) → develop (Developer teammate + Code-tester teammate + QA-tester teammate + Reviewer teammate) → report (no approval gate).

rube-de/cc-skills · 42 tokens