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 sahajamit/atlassian-cli --skill atl-jiragit clone --depth 1 https://github.com/sahajamit/atlassian-cliWrote 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/sahajamit/atlassian-cli/atl-jira)<a href="https://agentmods.dev/skills/sahajamit/atlassian-cli/atl-jira"><img src="https://agentmods.dev/badge/skills/sahajamit/atlassian-cli/atl-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.
<a href="https://agentmods.dev/skills/sahajamit/atlassian-cli/atl-jira"><img src="https://agentmods.dev/badge/skills/sahajamit/atlassian-cli/atl-jira.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.00032 | $0.02738 |
| Opus 5 | $0.00016 | $0.01369 |
| Sonnet 5 | $0.00006 | $0.00548 |
| Haiku 4.5 | $0.00003 | $0.00274 |
Grade A, and why
atl-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 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
atl — Jira Commands
Quick start
# Search issues
atl jira search "project = PROJ AND status != Done ORDER BY updated DESC"
# Read an issue
atl jira get-issue PROJ-123
# Create an issue
atl jira create-issue --project PROJ --type Bug --summary "Login broken"
# Transition an issue
atl jira transition-issue PROJ-123 --transition "In Progress"
# Add a comment
atl jira add-comment PROJ-123 "Investigating this now"
atl jira search <jql>
Search Jira issues using JQL.
atl jira search "<jql>" [--limit N] [--offset N] [--fields field1,field2] [--json]
Options:
--limit N(default: 20) — max results--offset N(default: 0) — skip N results--fields— comma-separated field names--json— force JSON output
Examples:
atl jira search "project = PROJ AND type = Bug AND status != Done"
atl jira search "assignee = currentUser() ORDER BY updated DESC"
atl jira search "project = PROJ AND updated >= -7d" --limit 50
JSON output:
{
"issues": [
{
"key": "PROJ-123",
"id": "10001",
"summary": "Issue title",
"status": "In Progress",
"statusCategory": "indeterminate",
"issueType": "Bug",
"priority": "High",
"assignee": "John Doe",
"reporter": "Jane Smith",
"created": "2024-01-15T10:30:00.000+0000",
"updated": "2024-01-16T14:20:00.000+0000",
"description": "Issue description in markdown",
"labels": ["backend", "urgent"],
"components": ["API"],
"comments": [],
"url": "https://company.atlassian.net/browse/PROJ-123"
}
],
"total": 42,
"hasMore": true
}
atl jira get-issue <key>
Get full details of a Jira issue including description and comments.
atl jira get-issue <ISSUE-KEY> [--comments N] [--fields field1,field2] [--json]
Options:
--comments N(default: 10) — max comments to include--fields— comma-separated field names--json— force JSON output
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 · 369 lines · 32 tokens per session scan A 3b9868553f84
atl-jira is a skill published in the GitHub repository sahajamit/atlassian-cli (8 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 2,738 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
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.