sumologic-documentation: Command for Claude Code

.claude/commands/jira.md

jira is a command for Claude Code from SumoLogic/sumologic-documentation. It costs 0 tokens per session (2,524 once invoked), scanned A, original, MIT.

A set of instructions for managing Sumo Logic documentation tickets in Jira, a system for tracking work and requests. It uses Atlassian's connected service to perform Jira operations.

In plain words
What is it for?
Creating and managing documentation tickets, applying project fields, and handling Jira access and ticket intake for the Sumo Logic documentation team.
Why use it?
It keeps ticket work tied to the DOCS project and prevents incorrect setup advice, such as installing an unsupported Jira command-line tool.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

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

Reuse

Borrowing it

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

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 jira

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/jira"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/jira.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 2,524 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.00000 $0.02524
Opus 5.5 $0.00000 $0.01010
Sonnet 5.5 $0.00000 $0.00505
Haiku 4.5 $0.00000 $0.00252

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

Security

Grade A, and why

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 17d 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/jira.md · 221 lines

How it starts

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

Jira – DOCS Project

You are helping manage Jira tickets for the Sumo Logic documentation team.

How Jira access works

All Jira operations use the Atlassian MCP server — there is no Jira CLI and you must never suggest installing one. If a Jira operation fails or tools are unavailable, the only correct response is:

"It looks like the Atlassian MCP server may not be connected. Run /mcp in Claude Code to check the connection status and authenticate."

Never suggest brew install jira, npm install jira-cli, or any other CLI tool as a fallback.

Project context

Ticket intake

External requests from Sumo Logic employees come in via the JSM portal: https://sumologic.atlassian.net/servicedesk/customer/portal/26/group/75/create/378

Tickets created via this command are created directly in the DOCS project and are distinct from portal-submitted requests.

Technical Area values

Assignee and due date are set automatically by Jira Automation based on Technical Area and Priority — do not set these manually.

Use this list to select the correct Technical Area when creating or updating tickets:

  • Alerts (Monitors, Sched. Search, Webhooks)
  • APIs
  • APM (Traces, RUM)
  • Apps/Integrations
  • Automation
  • Cloud SIEM
  • Cloud SOAR
  • Collectors/Sources
  • Dashboards
  • DojoAI
  • Getting Started (Product/Observability)
  • Getting Started (Security)
  • Log Search
  • Logs for Security
  • Manage (Administrator)
  • Manage (Analyst)
  • Manage (Data Forwarding)
  • Manage (Fields, FERs, Partitions, Data Tiers, Ingestion, Sched Views, Billing, Sharing)
  • Manage (Security, Users, Roles)
  • Metrics
  • Observability (AWSO)
  • Observability (Azure)
  • Observability (Kubernetes)
  • Observability (SLO)
  • Observability (Tracing)
  • Other
  • Other (Analytics)
  • Other (Optimization - GEO/SEO)
  • Other (Site Development & AI)
  • Platform Services
  • Sensu
  • Threat Intelligence

Read the full file on GitHub · 221 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. 17d ago Changed 7cb61f6e73bb
  2. 2mo ago First seen · 221 lines · 0 tokens per session scan A cdef4b5ff56e

Subscribe to this mod's changes

jira is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,524 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.

Related

jira compared with commands from other repositories

jira next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
jiraSumoLogic/sumologic-documentationCommand42yesterdayMITA0Claude Code
resume-cover-letterjezweb/claude-skillsCommand1.1k28d agoMITA12Claude Code
quotetdimino/claude-code-minoanCommand41yesterdayMITA0Claude Code
cliJNTMTMTM/eIslandCommand335yesterdayGPL-3.0A0Claude Code
canvasAgriciDaniel/claude-canvasCommand3037mo agoMITA25Claude Code
gpd:settingspsi-oss/get-physics-doneCommand9733mo agononeA36Claude Code
gpd:updatepsi-oss/get-physics-doneCommand9733mo agononeA14Claude Code