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 darellchua2/opencode-config-template --skill pr-merge-workflow-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/pr-merge-workflow-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/pr-merge-workflow-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/pr-merge-workflow-skill.svg" alt="Measured on agentmods" 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.00057 | $0.01641 |
| Opus 5 | $0.00028 | $0.00821 |
| Sonnet 5 | $0.00011 | $0.00328 |
| Haiku 4.5 | $0.00006 | $0.00164 |
Grade A, and why
pr-merge-workflow-skill 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Merge + Monitor + Fix Workflow
Use when the user says phrases like "pr merge to main", "merge the PR to develop", "merge to [branch]", "complete the PR", or "merge it". This skill handles everything after the PR is approved and ready to merge.
Prerequisites
Before executing, confirm:
- Current branch has an open PR targeting the specified branch
- PR is in a mergeable state (no conflicts, reviews passed)
- If not, tell the user what's blocking and stop
Phase 1: Merge the PR
- Get PR info:
gh pr view --json number,url,headRefName,baseRefName,title,state,mergeable - Verify state is
OPENand mergeable isMERGEABLE - Merge using squash (default):
gh pr merge <number> --squash --delete-branch=false- If user prefers merge commit:
gh pr merge <number> --merge --delete-branch=false - Do NOT auto-delete branch yet — wait for CI
- If user prefers merge commit:
- Record: PR number, source branch name, target branch name, JIRA ticket key (if any)
Phase 2: Monitor GitHub Actions CI
- Find the post-merge CI run:
gh run list --branch <target-branch> --limit 1 - If no CI workflow exists, skip to Phase 4 (no CI to monitor)
- Monitor the run:
- Use
gh run view <run-id>to check status - Poll every 30 seconds if still
in_progress - Maximum wait: 10 minutes (configurable by user)
- Use
- Possible outcomes:
completed+conclusion: success→ Phase 4completed+conclusion: failure→ Phase 3- Timeout → Report to user, ask how to proceed
Phase 3: Fix CI Failures (Auto-Heal Loop)
This phase loops until CI passes or max retries hit (default: 3 attempts).
Step 3a: Diagnose
- Get failure logs:
gh run view <run-id> --log-failed - Identify failing job and step
- Determine if the failure is fixable by code changes (lint errors, test failures, type errors) or requires human intervention (infrastructure issues, secret rotation)
Step 3b: Fix
For auto-fixable failures:
- Checkout the target branch:
git checkout <target-branch> && git pull - Create a fix branch:
git checkout -b fix/ci-<run-id> - Read the failing files and apply fixes
- Commit with message:
fix(ci): resolve <error-type> from run <run-id> - Push and create PR:
gh pr create --base <target-branch> --title "fix(ci): ..." --body "..." - Merge immediately if trivial:
gh pr merge <number> --squash --delete-branch
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 First seen · 165 lines · 57 tokens per session scan A f7ba5fbdf350
pr-merge-workflow-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 1,641 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
maintainer-release-ops
Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, assess milestone health, coordinate release blockers, or generate a release-focused review brief.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.