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 decocms/studio --skill jira-mergegit clone --depth 1 https://github.com/decocms/studioWrote 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/decocms/studio/jira-merge)<a href="https://agentmods.dev/skills/decocms/studio/jira-merge"><img src="https://agentmods.dev/badge/skills/decocms/studio/jira-merge/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/decocms/studio/jira-merge"><img src="https://agentmods.dev/badge/skills/decocms/studio/jira-merge.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.00054 | $0.00965 |
| Opus 5.5 | $0.00022 | $0.00386 |
| Sonnet 5.5 | $0.00011 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
jira-merge 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 27d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-merge — land it and move the cards
Insert this into the prompt of a run you start on several issues at once ("one
run for all of them"), or of the Jira column your team ships from. Either way
the issues are in your opening message, web links included, and every Jira
tool takes issueKey to say which issue it is about. On a run about one issue
you can leave it out.
It is ordinary text once inserted — read it, cut what does not apply to your team, add what does.
You are landing work that has already been implemented and reviewed: the issues above, each carrying its pull request(s) as web links.
Find what you are landing
- The pull requests are on each issue as web links. An issue can carry more than one, in different repositories — a change that spans two storefronts opens one in each, and both are the delivery.
- Ignore a link to a pull request that is already closed or merged, and links
another team's automation left.
gh pr view <url> --json state,mergeabletells you. - An issue with no open pull request gets a comment saying so and nothing else.
Order
Merging one pull request moves the base under the next, so land them one at a time, in the order the issues are listed, and re-check the next one's mergeability after each merge rather than trusting what you read at the start.
Check before you merge
- Already merged? Say so in a comment and move on to the card. Do not re-merge, and do not open anything.
- Checks red? Read them (
gh pr checks <url>, then the failing run's log) before deciding. A check that fails the same way on the base branch is not this change's fault — say that in your comment and merge. A check that fails because of this change is a stop for THAT issue: comment what broke, leave its card where it is, and carry on with the next issue. - Blocked by branch protection or a missing approval? That needs a human. Report it on the issue and move to the next one; do not try to route around it.
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.
- 27d ago First seen · 84 lines · 54 tokens per session scan A 7429c0566dea
jira-merge is a skill published in the GitHub repository decocms/studio (409 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 965 once invoked, about $0.0002 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-19.
Other skills, from other repositories
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
pn-github-vertical-slices
Break a plan or PRD into tracer-bullet vertical slices and create GitHub Issues via GitHub MCP (official github/github-mcp-server). Dependencies first (AFK/HITL). Use after pn-writing-plans or pn-create-prd when work must ship as Issues.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
map-diff
Analyze the impact of staged git changes against the committed Cortex function knowledge graph — shows which downstream functions are affected before you commit.