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.
npx skills add bmbouter/redhat-agents --skill jira-setupgit clone --depth 1 https://github.com/bmbouter/redhat-agentsWrote 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.
[](https://agentmods.dev/skills/bmbouter/redhat-agents/jira-setup)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/jira-setup"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/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.
<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/jira-setup"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/jira-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00023 | $0.00628 |
| Opus 5.5 | $0.00009 | $0.00251 |
| Sonnet 5.5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Run this before using any Jira-connected agents. Required once per machine.
Instructions
Walk the user through the following steps. Pause after each step and confirm before proceeding.
Step 1: Check for existing Atlassian MCP configuration
Check whether the user's AI tool already has Atlassian MCP tools configured. Look for an existing mcp__plugin_atlassian_atlassian__ tool prefix or similar Atlassian/Jira integration.
If already configured, skip to Step 4 (verification).
Step 2: Create an Atlassian API token
Tell the user:
To connect to Jira, you need an Atlassian API token. Follow these steps:
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Click Create API token
- Give it a name like "AI Agent Access"
- Copy the token — you will not be able to see it again
Paste the token here when ready.
Wait for the user to provide the token. Do NOT store the token in any file — it should only go into the MCP configuration.
Step 3: Configure MCP settings
The Atlassian MCP plugin needs the following configuration. Guide the user to add this to their AI tool's MCP settings (e.g., Claude Code's settings.json, .claude.json, or equivalent):
{
"mcpServers": {
"atlassian": {
"type": "plugin",
"id": "atlassian",
"config": {
"atlassianEmail": "<user's email>",
"atlassianApiToken": "<token from step 2>",
"atlassianUrl": "https://<instance>.atlassian.net"
}
}
}
}
Ask the user for:
- Their Atlassian email address
- Their Jira instance URL (e.g.,
https://yourcompany.atlassian.net) - The API token from Step 2
Help them place the configuration in the correct file for their tool.
Step 4: Verify connectivity
Test the connection by searching for a known project:
searchJiraIssuesUsingJql:
jql: "project = <project_key> ORDER BY updated DESC"
maxResults: 1
If this succeeds, tell the user Jira is connected and ready.
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.
- 1mo ago First seen · 85 lines · 23 tokens per session scan A 0fb533991dfd
jira-setup is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 628 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.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…