clone-from-github

clone-from-github is a command for Claude Code from openshift-eng/ai-helpers. It costs 11 tokens per session (3,294 once invoked), scanned A, original, Apache-2.0.

A command that copies GitHub issues into Jira while preserving their content and linking the new Jira tickets to the originals. GitHub is a code-hosting service, while Jira is a work-tracking system.

In plain words
What is it for?
Use it to migrate one or more GitHub issues, import upstream work into Jira, or create Jira tickets linked to GitHub issues.
Why use it?
It avoids re-entering issues by hand when moving work between GitHub and Jira. The links help teams follow the same issue across both systems.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Part of the jira plugin — 13 skills, 17 commands shipped together

Good fit Use it to migrate one or more GitHub issues, import upstream work into Jira, or create Jira tickets linked to GitHub issues.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/openshift-eng/ai-helpers/clone-from-github
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/openshift-eng/ai-helpers

Made for: Claude Code.

Or install jira, the plugin that ships this one along with the rest of its 13 skills, 17 commands.

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 clone-from-github

README.md
[![agentmods](https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/clone-from-github/github.svg)](https://agentmods.dev/commands/openshift-eng/ai-helpers/clone-from-github)
Your own site
<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/clone-from-github"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/clone-from-github/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 clone-from-github

Your own site · 80×15
<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/clone-from-github"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/clone-from-github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,294 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.00011 $0.03294
Opus 5.5 $0.00004 $0.01318
Sonnet 5.5 $0.00002 $0.00659
Haiku 4.5 $0.00001 $0.00329

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

Security

Grade A, and why

clone-from-github 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/jira/commands/clone-from-github.md · 427 lines

How it starts

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

Name

jira:clone-from-github

Synopsis

/jira:clone-from-github <issue-number> [issue-number...] [options]

Description

The jira:clone-from-github command clones one or more GitHub issues to Jira, preserving the original issue content and establishing a link between the GitHub and Jira issues. This command is useful for:

  • Migrating GitHub issues to Jira for project tracking
  • Creating Jira tickets that track upstream GitHub issues
  • Maintaining synchronization between GitHub and Jira workflows
  • Bulk importing GitHub issues into Jira projects

The command uses the gh2jira utility to perform the cloning operation. Use /jira:setup-gh2jira to install and configure gh2jira if you haven't already.

Implementation

📋 Phase 1: Validate Prerequisites and Locate Installation

Check that the gh2jira utility is available and configured:

  1. Locate gh2jira binary and installation directory:

    # Find the gh2jira binary
    GH2JIRA_BIN=$(which gh2jira 2>/dev/null)
    
    if [ -z "$GH2JIRA_BIN" ]; then
      echo "gh2jira not found. Run /jira:setup-gh2jira to install."
      exit 1
    fi
    
    # If it's a symlink, resolve it to find the actual installation
    if [ -L "$GH2JIRA_BIN" ]; then
      GH2JIRA_BIN=$(readlink "$GH2JIRA_BIN")
    fi
    
    # Get the directory containing the gh2jira binary
    GH2JIRA_DIR=$(dirname "$GH2JIRA_BIN")
    
    echo "Found gh2jira at: $GH2JIRA_DIR"
    
  2. Verify configuration files exist in installation directory:

    cd "$GH2JIRA_DIR" || exit 1
    
    # Check for tokenstore.yaml
    if [ ! -f "tokenstore.yaml" ]; then
      echo "tokenstore.yaml not found in $GH2JIRA_DIR"
      echo "Run /jira:setup-gh2jira to configure authentication."
      exit 1
    fi
    
    # Check for profiles.yaml (optional)
    if [ -f "profiles.yaml" ]; then
      echo "Found profiles.yaml"
    fi
    
  3. Verify tokens are configured:

    • Check that tokenstore.yaml contains actual tokens (not placeholder values)
    • GitHub token should not contain "YOUR_GITHUB_TOKEN"
    • Jira token should not contain "YOUR_JIRA_API_TOKEN"

Read the full file on GitHub · 427 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. 1mo ago First seen · 427 lines · 11 tokens per session scan A 4d0e9755f716

Subscribe to this mod's changes

clone-from-github is a command published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 3,294 once invoked, about $0.0000 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-09-03.