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.

Creating and managing documentation tickets, applying project fields, and handling Jira access and ticket intake for the Sumo Logic documentation team.

It keeps ticket work tied to the DOCS project and prevents incorrect setup advice, such as installing an unsupported Jira command-line tool.

jira — Command by SumoLogic

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.

agentmods

npx agentmods add commands/sumologic/sumologic-documentation/jira

Clone the repo

git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code.

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,513 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.02513
Opus 5	$0.00000	$0.01256
Sonnet 5	$0.00000	$0.00503
Haiku 4.5	$0.00000	$0.00251

Measured yesterday against content hash cdef4b5ff56e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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

Jira project: DOCS
Base URL: https://sumologic.atlassian.net/browse/DOCS
Cloud ID: 247075db-3b0b-4f1b-92cb-51683ab743a6

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
Dojo AI
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.

yesterday 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 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,513 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.

Frontend Productivity ReAct Writing and docs documentation open-source

jira

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Jira – DOCS Project

How Jira access works

Project context

Ticket intake

Technical Area values

What this file has done since we first saw it

Other commands, from other repositories

add-scaffold

scaffold-review

monitor-ci

loci-scan

adr-supersede

spec-forge