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 mfmezger/ai_agent_dotfiles --skill jira-datacentergit clone --depth 1 https://github.com/mfmezger/ai_agent_dotfilesWrote 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/mfmezger/ai_agent_dotfiles/jira-datacenter)<a href="https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/jira-datacenter"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/jira-datacenter/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/mfmezger/ai_agent_dotfiles/jira-datacenter"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/jira-datacenter.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.00046 | $0.01588 |
| Opus 5 | $0.00023 | $0.00794 |
| Sonnet 5 | $0.00009 | $0.00318 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
jira-datacenter 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 9d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Data Center
Interact with Jira Data Center/Server instances via REST API.
Features
| Command | Description |
|---|---|
| get | Get issue details by key |
| search | Search issues using JQL |
| create | Create a new issue |
| update | Update issue fields |
| transition | Change issue status |
| comment | Add a comment to an issue |
| assign | Assign issue to a user |
| projects | List available projects |
| transitions | List available transitions for an issue |
Prerequisites
Environment variables (can be in .env file):
JIRA_BASE_URL- Your Jira instance URL (e.g.,https://jira.company.com)JIRA_PAT- Personal Access Token (preferred)
OR for basic auth:
JIRA_BASE_URL- Your Jira instance URLJIRA_USERNAME- Your usernameJIRA_PASSWORD- Your password
Creating a Personal Access Token
- Go to your Jira profile (click avatar → Profile)
- Navigate to Personal Access Tokens
- Click "Create token"
- Give it a name and set expiry
- Copy the token to
JIRA_PAT
Usage
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py COMMAND [OPTIONS]
Commands
Get Issue
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py get PROJ-123
Options:
--fields FIELD1,FIELD2- Specific fields to return (default: all)--comments- Include comments--json- Output as JSON
Search Issues (JQL)
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py search "project = PROJ AND status = Open"
Options:
--max N- Maximum results (default: 50)--fields FIELD1,FIELD2- Fields to include--json- Output as JSON
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 203 lines · 46 tokens per session scan A e02cdd428d40
jira-datacenter is a skill published in the GitHub repository mfmezger/ai_agent_dotfiles (5 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,588 once invoked, about $0.0002 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
launch
Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort…
omc-plan
Strategic planning with optional interview workflow.
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
ask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…
ultragoal
Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.