Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitnpx agentmods add skills/ulises-jeremias/agent-toolkit/jira-collaborationWrote 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/ulises-jeremias/agent-toolkit/jira-collaboration)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/jira-collaboration"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/jira-collaboration/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/ulises-jeremias/agent-toolkit/jira-collaboration"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/jira-collaboration.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.00033 | $0.02501 |
| Opus 5 | $0.00016 | $0.01251 |
| Sonnet 5 | $0.00007 | $0.00500 |
| Haiku 4.5 | $0.00003 | $0.00250 |
Grade A, and why
jira-collaboration 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 8d 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.
This is a copy
89% identical to jira-collaboration — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-collaborate
Collaboration features for JIRA issues - comments, attachments, watchers, and notifications.
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| List comments/attachments | - |
Read-only |
| List watchers | - |
Read-only |
| View activity history | - |
Read-only |
| Add comment | - |
Easily reversible (can delete) |
| Upload attachment | - |
Easily reversible (can delete) |
| Add watcher | - |
Can remove watcher |
| Send notification | - |
Cannot unsend but harmless |
| Update comment | ! |
Previous text lost |
| Update custom fields | ! |
Can be undone via edit |
| Remove watcher | ! |
Can re-add |
| Delete comment | !! |
Comment text lost |
| Delete attachment | !! |
File lost, must re-upload |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
When to use this skill
Use this skill when you need to:
- Add, update, or delete comments on issues
- Upload or download attachments
- Manage watchers (add/remove)
- Send notifications to users or groups
- View issue activity and changelog
What this skill does
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
- Comments: Add/edit/delete comments with rich text support
- Attachments: Upload and download files
- Watchers: Manage who tracks the issue
- Notifications: Send targeted notifications
- Activity History: View issue changelog
- Custom Fields: Update custom field values
Available Commands
Comments
| Command | Description |
|---|---|
jira-as collaborate comment add |
Add comment with visibility controls |
jira-as collaborate comment update |
Update existing comment |
jira-as collaborate comment delete |
Delete comment (with confirmation) |
jira-as collaborate comment list |
List and search comments |
Attachments
| Command | Description |
|---|---|
jira-as collaborate attachment list |
List attachments on issue |
jira-as collaborate attachment upload |
Upload file to issue |
jira-as collaborate attachment download |
Download attachments |
What ships with it
3 files 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.
- 8d ago First seen · 299 lines · 33 tokens per session scan A 52c4e608a609
jira-collaboration is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (17 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,501 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to jira-collaboration, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
jira-collaboration
Collaborate on issues: add/edit comments, share attachments, notify users, track activity. For team communication and coordination on JIRA issues.
iblai-api-agent-support
Manage an ibl.ai agent's human-support tickets via the platform API — list and filter the tickets users raised with an agent (by agent, requester, status, session), read a ticket's conversation thread, reply as the support team, change ticket status, and close or delete tickets. Use when triaging or responding to…
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…
breaking-down-work
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a deliverable, or build a work breakdown…
capturing-meeting-actions
Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this".
mapping-dependencies
Maps task dependencies in an Astravue project, finds the critical path and blocked work, and detects circular dependencies before any rescheduling. Use when the user asks about dependencies, blockers, what's blocking what, the critical path, or wants to understand or fix the sequencing of a project.