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 paultyng/skill-issue --skill create-jira-itemgit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/create-jira-item)<a href="https://agentmods.dev/skills/paultyng/skill-issue/create-jira-item"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/create-jira-item/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/paultyng/skill-issue/create-jira-item"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/create-jira-item.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.00048 | $0.00535 |
| Opus 5 | $0.00024 | $0.00267 |
| Sonnet 5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
create-jira-item 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.
What it actually says
Create Jira Item
Create Jira issues using the Atlassian MCP, with proper custom field handling.
1. Determine Target
- Project: Use the project specified by the user. If not specified, infer by searching the user's recent issues (
searchJiraIssuesUsingJqlwith(assignee = currentUser() OR reporter = currentUser()) ORDER BY updated DESC). If inference fails, ask. - Issue type: story, epic, task, initiative, etc. Infer from context or ask.
2. Introspect Custom Fields
Before creating the issue, discover the project's field requirements:
-
Get available issue types via
getJiraProjectIssueTypesMetadata(cloudId, projectIdOrKey). -
Get field metadata for the chosen issue type via
getJiraIssueTypeMetaWithFields(cloudId, projectIdOrKey, issueTypeId). -
Pay attention to:
- Required fields that are not standard (e.g., "Team", "Quarter", "Initiative Link", "Sprint")
- Custom field IDs (
customfield_NNNNN) -- use these in the create call - Allowed values for select/multi-select fields
For epics and initiatives especially, org-specific fields are common and must be populated. Do not rely on default field assumptions.
3. Create the Issue
Use createJiraIssue with:
- Summary: terse, descriptive title
- Description: terse. Bullet points preferred. No boilerplate.
- Assignee: current user (use
lookupJiraAccountIdif needed) - Priority: Medium unless user specifies otherwise
- All required custom fields populated from step 2
4. Link to Epic (if applicable)
If the issue should be under an epic:
- Use
createIssueLinkor set the epic link field (varies by Jira config) - If the user mentions an epic by name or key, search for it first via
searchJiraIssuesUsingJql(cloudId, "project = X AND issuetype = Epic AND summary ~ 'name'").
5. Report
Return the issue key and URL. If any required fields were unknown or couldn't be populated, note them.
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 · 47 lines · 48 tokens per session scan A de414d49235d
create-jira-item is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 535 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
confluence-assistant
Central hub for Confluence operations - routes requests to specialized skills. ALWAYS use when user mentions confluence, wiki, or Atlassian wiki operations.
confluence-template
Work with page templates and blueprints. ALWAYS use when user wants to create standardized pages or manage templates.
confluence-admin
Confluence administration including users, groups, space settings, and permission diagnostics. Use when managing user access, group membership, viewing space configuration, or checking permissions.
confluence-bulk
Bulk operations for 50+ pages - updates, moves, deletions, labels, and permissions. Use when updating multiple pages simultaneously (dry-run preview included), needing rollback safety, or coordinating team changes. Handles partial failures gracefully.
confluence-jira
JIRA integration - embed issues, create links between products. ALWAYS use when user wants to connect Confluence and JIRA.
workflow-client-bootstrap
WHAT — Interactive interview to capture client delivery context and store it inside the user's /.ai-workspace (or similar) as packs + knowledge (no client skills). Use when onboarding a new client project or updating an existing workspace context.