Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/darellchua2/opencode-config-templatenpx agentmods add skills/darellchua2/opencode-config-template/git-pr-creatorWrote 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/git-pr-creator)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/git-pr-creator"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/git-pr-creator/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/darellchua2/opencode-config-template/git-pr-creator"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/git-pr-creator.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.00037 | $0.04917 |
| Opus 5.5 | $0.00015 | $0.01967 |
| Sonnet 5.5 | $0.00007 | $0.00983 |
| Haiku 4.5 | $0.00004 | $0.00492 |
Grade A, and why
git-pr-creator 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 1mo 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.
if curl -s -o /dev/null -w "%{http_code}" "$image_path" | grep -q "200"; then How it starts
The opening of the file, as written. The whole thing — 639 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I implement a complete Git PR creation workflow with optional JIRA integration:
- Check JIRA Integration: Ask user if JIRA is used for the project
- Create Pull Request: Create a GitHub/GitLab PR with comprehensive description
- Use git-semantic-commits: Format PR title following Conventional Commits specification
- Apply Semantic Versioning Label: Auto-apply major/minor/patch label based on PR title
- Scan for Diagrams/Images: Search for workflow-related images and diagrams
- Attach Images to JIRA: Upload local/temporary images directly to JIRA (not just links)
- Add JIRA Comments: Use
git-issue-updaterto create comments with PR details and attachments - Update JIRA Status (Optional): Delegate to
jira-status-updaterto transition ticket status after manual merge
When to use me
Use this workflow when:
- You've completed work on a feature or fix and need to create a PR
- You want to update JIRA tickets with PR information
- You have diagrams or images that need to be attached to JIRA (not just linked)
- You need to ensure JIRA tickets are updated with actual image files for visibility
- You want to maintain traceability between PRs and JIRA tickets
Prerequisites
- Git repository with commits to push
- GitHub CLI (
gh) or GitLab CLI (glab) installed and authenticated - If using JIRA: Atlassian account with appropriate permissions
- JIRA cloud ID and project key
- Existing JIRA ticket(s) to update
Steps
Step 1: Check Git Status
- Verify current git status:
git status - Ensure all changes are committed
- Check for uncommitted changes that need attention
Step 2: Ask About JIRA Integration
- Prompt the user: "Is JIRA used for this project? (yes/no)"
- If yes, proceed with JIRA integration steps
- If no, skip JIRA-related steps and only create the PR
Step 3: Get JIRA Ticket Information (if JIRA is used)
- Ask the user for the JIRA ticket ID (e.g., "IBIS-101")
- Verify the ticket exists using Atlassian MCP tools
- Get the cloud ID if not provided
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.
- 1mo ago First seen · 639 lines · 37 tokens per session scan A ef8ce19eb6f1
git-pr-creator is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 28d ago), licensed Apache-2.0. It adds 37 tokens to every session and 4,917 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.