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 ticket-to-code-changegit 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/ticket-to-code-change)<a href="https://agentmods.dev/skills/openhands/extensions/ticket-to-code-change"><img src="https://agentmods.dev/badge/skills/openhands/extensions/ticket-to-code-change/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/ticket-to-code-change"><img src="https://agentmods.dev/badge/skills/openhands/extensions/ticket-to-code-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.00549 |
| Opus 5.5 | $0.00034 | $0.00220 |
| Sonnet 5.5 | $0.00017 | $0.00110 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
ticket-to-code-change 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket to code change
Create an automation that turns implementation-ready tickets into tested pull requests or merge requests.
Information to collect
Ask the user for:
- The issue tracker: Linear. Jira automations are set up with the
jira-issue-to-prskill instead, which ships a poller. - The source-control provider: GitHub, GitLab, or Bitbucket Cloud.
- The project or team to watch and the label or workflow state that means "implementation ready".
- How a ticket identifies its target repository and base branch.
- The polling schedule or issue event to use.
- The ticket state to set when work starts and when the change request opens.
- Whether linked dependencies must be completed before dispatch.
Setup workflow
- Verify that both required integrations are connected and can read the selected project and repository.
- Prefer an issue event trigger when the deployment can receive events; otherwise use cron polling with durable issue-ID deduplication.
- Limit each run to a small configurable number of new tickets. On initial deployment, establish a baseline instead of dispatching the entire backlog.
- Build a prompt that includes the full ticket, acceptance criteria, dependency status, repository, base branch, and provider-specific request terminology. Require the agent to run the repository's tests before opening the pull request or merge request.
- Create the automation through the Automation backend's prompt-preset
endpoint. On OpenHands Cloud or Enterprise the backend is the
<HOST>value in your system prompt, authenticated withAuthorization: Bearer $OPENHANDS_API_KEY. On a local Agent Canvas it is the Automation backend described in<RUNTIME_SERVICES>, authenticated with the runtime-provided automation API key. - Configure the automation to post the OpenHands conversation URL immediately and the resulting pull-request or merge-request URL back to the ticket.
Do not dispatch tickets with unresolved dependencies or without an unambiguous target repository; comment on the ticket with the missing information instead.
What ships with it
5 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 · +2 lines · +13 tokens per session 7db317dea372
- 14d ago Changed · +3 lines d590187f7b03
- 1mo ago First seen · 51 lines · 71 tokens per session scan A 1d063f120e12
ticket-to-code-change is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 549 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
implement-issue
Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.