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 agentmods add skills/bmbouter/redhat-agents/jira-setupnpx skills add bmbouter/redhat-agents --skill jira-setupgit clone --depth 1 https://github.com/bmbouter/redhat-agentsWhat 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.00023 | $0.00628 |
| Opus 5 | $0.00012 | $0.00314 |
| Sonnet 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 2d 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.
- 2d 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 (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 628 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…