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 daxaur/openpaw --skill c-jiragit clone --depth 1 https://github.com/daxaur/openpawWrote 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/daxaur/openpaw/c-jira)<a href="https://agentmods.dev/skills/daxaur/openpaw/c-jira"><img src="https://agentmods.dev/badge/skills/daxaur/openpaw/c-jira.svg" alt="Measured on agentmods" 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.00045 | $0.00491 |
| Opus 5 | $0.00023 | $0.00246 |
| Sonnet 5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
c-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.
What it actually says
What This Skill Does
Uses jira (jira-cli) to interact with Jira projects — listing issues, creating tickets, moving issues through workflow transitions, and managing sprints.
CLI Tool: jira
List & View Issues
jira issue list # List issues assigned to you
jira issue list --project MYPROJ # Filter by project
jira issue list --status "In Progress" # Filter by status
jira issue list --type Bug # Filter by issue type
jira issue view MYPROJ-123 # View issue details
Create Issues
jira issue create \
--project MYPROJ \
--type Bug \
--summary "Login page throws 500 error" \
--body "Steps to reproduce: ..." \
--priority High \
--label backend
Transitions
jira issue move MYPROJ-123 "In Progress"
jira issue move MYPROJ-123 "Done"
jira issue move MYPROJ-123 "In Review"
Comments
jira issue comment add MYPROJ-123 --body "Fixed in PR #456"
Sprints
jira sprint list --project MYPROJ # List sprints
jira sprint add MYPROJ-123 --sprint 42 # Add issue to sprint
Usage Guidelines
- Always use the full issue key (e.g.,
MYPROJ-123) in commands. - Run
jira issue listbefore creating tickets to check for existing duplicates. - Use
jira issue moveto transition issues — confirm the valid transition names withjira issue viewfirst. - When the user says "close" or "resolve" an issue, use the appropriate transition name for their workflow.
Notes
- Requires
jira initto configure server URL and credentials before use. - Install:
brew install ankitpokhrel/jira-cli/jira-cli
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 · 67 lines · 45 tokens per session scan A b3db5ada2642
c-jira is a skill published in the GitHub repository daxaur/openpaw (167 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 491 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-30.
Other skills, from other repositories
linear
Linear project management — issues, cycles, and projects via GraphQL API.
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
jira-service-management
Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.
jira-time-tracking
Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…
jira-custom-fields
Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA…
jira-issue-management
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile)…