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 OpenHands/extensions --skill jira-issue-to-prgit clone --depth 1 https://github.com/OpenHands/extensionsWrote 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/openhands/extensions/jira-issue-to-pr)<a href="https://agentmods.dev/skills/openhands/extensions/jira-issue-to-pr"><img src="https://agentmods.dev/badge/skills/openhands/extensions/jira-issue-to-pr/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/openhands/extensions/jira-issue-to-pr"><img src="https://agentmods.dev/badge/skills/openhands/extensions/jira-issue-to-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 103 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- high Supply Chain · line 114 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- high Supply Chain · line 135 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- high Supply Chain · line 140 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- medium Data Exfiltration · line 103 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 114 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 154 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00219 | $0.05237 |
| Opus 5.5 | $0.00088 | $0.02095 |
| Sonnet 5.5 | $0.00044 | $0.01047 |
| Haiku 4.5 | $0.00022 | $0.00524 |
Grade A, and why
jira-issue-to-pr scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Set `OPENHANDS_HOST` and `AUTH_HEADER` for the curl commands below: How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira → Pull Request Automation (GitHub, GitLab, Bitbucket)
Deploys a cron automation that polls a Jira Cloud instance for open issues carrying a
configurable label and, for each new issue, starts an OpenHands agent conversation that
clones the repository specified in the ticket body on the configured git provider (GitHub
by default, GitLab or Bitbucket with git_provider), creates a branch, implements or
placeholders the requested change, and opens a pull request (a merge request on GitLab).
Once the conversation
starts, it also posts a comment on the Jira ticket: "I'm on it: <conversation URL>".
How It Works
- Poll - every N minutes, search the Jira Cloud instance for open issues with the
configured label: through the user's connected Atlassian Rovo MCP server on OpenHands
Cloud and Enterprise, or with
POST /rest/api/3/search/jqland an API token. - Deduplicate - on the very first run the script records a
first_run_atbaseline timestamp in the KV store; any issue whoseupdatedtimestamp predates that baseline is skipped (no backfill blast on first deploy). Usingupdatedrather thancreatedmeans an old issue that has its label added after the automation is deployed will still be picked up. Subsequent runs filter by bothfirst_run_atand a KV-backed set of already-processed issue keys. Amax_new_per_runcap (default 5) limits conversations started per cron firing as additional defense-in-depth. - Dispatch - for each new issue, start an independent agent conversation with a
PR-creation prompt:
POST /api/conversationson the agent server when running locally, orPOST /api/v1/app-conversationson OpenHands Cloud. The prompt instructs the agent to extract the target repository (owner/repoon GitHub;group/projector a URL on GitLab;workspace/repoon Bitbucket) from the ticket body. - Comment - immediately after the conversation is created, post a Jira comment on the
issue:
I'm on it: <conversation URL>. - Persist - record the processed issue key so re-runs never duplicate work.
What ships with it
7 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.
- 4d ago Changed · +49 lines · +68 tokens per session 81bd298fd5b9
- 14d ago Changed · +111 lines 5ffb5f6dda7d
- 1mo ago First seen · 217 lines · 151 tokens per session scan A e5c143d6c025
jira-issue-to-pr is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 219 tokens to every session and 5,237 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gsd-quick-batch
Batch several /gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
deliver-spec
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.