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 itseffi/agentic-os --skill atlassian-jira-syncgit clone --depth 1 https://github.com/itseffi/agentic-osWrote 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/itseffi/agentic-os/atlassian-jira-sync)<a href="https://agentmods.dev/skills/itseffi/agentic-os/atlassian-jira-sync"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/atlassian-jira-sync/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/itseffi/agentic-os/atlassian-jira-sync"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/atlassian-jira-sync.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.00026 | $0.00518 |
| Opus 5.5 | $0.00010 | $0.00207 |
| Sonnet 5.5 | $0.00005 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
atlassian-jira-sync 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.
What it actually says
Jira Issue Sync
Check Jira for assigned issues and sync with local task management.
Instructions
Step 1: Fetch Assigned Issues
Call jira_search with JQL:
assignee = currentUser() AND status != Done ORDER BY priority DESC
Step 2: Compare with Local Tasks
Check Tasks/ for existing files with Jira references:
- Look for
jira_keyin YAML frontmatter - Identify new issues not yet in Tasks/
Step 3: Present Summary
Jira Issues (8 active):
**Blockers/Critical**
- PROJ-123: Production bug in auth [In Progress]
**High Priority**
- PROJ-124: API rate limiting [To Do]
- PROJ-125: Update deployment docs [In Review]
**Normal**
- PROJ-126: Refactor logging [Backlog]
3 issues not yet in local Tasks. Create them?
Step 4: Sync Options
| Option | Description |
|---|---|
| Create all | Add all new issues as local tasks |
| Select specific | Choose which to sync |
| Skip | Continue without syncing |
Step 5: Create Local Tasks
For each issue to sync, create task file:
---
title: [Issue summary]
category: technical
priority: [Map from Jira priority]
status: n
jira_key: PROJ-XXX
---
Priority Mapping
| Jira | Personal OS |
|---|---|
| Blocker | P0 |
| Critical | P0 |
| High | P1 |
| Medium | P2 |
| Low | P3 |
Example Flow
User: "What should I work on today?"
Agent:
- Fetches Jira issues
- Compares with local tasks
- "You have 5 Jira tickets..."
- Offers to create local tasks
- Continues with planning
Notes
- Keep
jira_keyin frontmatter for bidirectional sync - Update Jira status when local task completes
- Include Jira link in task context section
When to Use
Use this skill when the task directly matches the workflow described above.
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
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.
- 1mo ago First seen · 99 lines · 26 tokens per session scan A 4c153a63e133
atlassian-jira-sync is a skill published in the GitHub repository itseffi/agentic-os (117 stars, last pushed 20d ago), licensed MIT. It adds 26 tokens to every session and 518 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-30.
Other skills, from other repositories
prismer-notion
Notion API + ntn CLI: pages, databases, markdown, Workers.
prismer-teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.
prismer-apple-reminders
Apple Reminders via remindctl: add, list, complete.
meeting-actions
Turn supplied meeting notes or transcripts into cited decisions, commitments, unresolved questions, and deduplicated Prismer tasks.
weekly-review
Review commitments and stalled work from Prismer tasks and memory, then produce an evidence-based weekly plan with explicit coverage gaps.
slack-tools
Slack workspace management and automation specialist.