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 mir-am/skills-agents-ai-coding --skill gh-cr-submitgit clone --depth 1 https://github.com/mir-am/skills-agents-ai-codingWrote 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/mir-am/skills-agents-ai-coding/gh-cr-submit)<a href="https://agentmods.dev/skills/mir-am/skills-agents-ai-coding/gh-cr-submit"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-cr-submit/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/mir-am/skills-agents-ai-coding/gh-cr-submit"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-cr-submit.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.00020 | $0.04098 |
| Opus 5 | $0.00010 | $0.02049 |
| Sonnet 5 | $0.00004 | $0.00820 |
| Haiku 4.5 | $0.00002 | $0.00410 |
Grade A, and why
gh-cr-submit 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 9d 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 — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Extract PR number from user input (supports
#123,PR 123,pull request 123) - Validate GitHub CLI installed and authenticated
- Validate GitHub remote exists
- Verify PR exists on GitHub
- Get current local branch and PR target branch
- Handle fork scenarios (cross-repo PRs)
- Ask user approval if local branch doesn't match PR target
- Search for review file in
.opencode/review/matching PR number - Handle multiple review files (ask user to choose)
- Read review file content
- Prepend AI-generated warning header at the very top
- Submit review as comment (neutral stance) to GitHub PR
- Report success with PR URL
When to use me
Use this skill when the user asks to submit a code review to a GitHub Pull Request.
Trigger examples:
- "Submit review for PR #123"
- "Post the review to PR 456"
- "Submit code review for pull request 789"
- "Upload review to PR #123"
Prerequisites
-
GitHub CLI installed:
ghmust be available- Check:
command -v gh >/dev/null 2>&1 - If not found: "Error: GitHub CLI not found. Install from: https://cli.github.com/"
- Check:
-
Authenticated with GitHub: User must be logged in
- Check:
gh auth status - If not authenticated: "Error: Not authenticated with GitHub. Run: gh auth login"
- Check:
-
GitHub remote: Repository must have a GitHub remote configured
- Check:
gh repo view --json nameWithOwner - If fails: "Error: This repository does not have a GitHub remote configured."
- Check:
-
Review file exists: Must have review file in
.opencode/review/- Check:
.opencode/review/directory exists - If not: "Error: .opencode/review/ directory not found. Generate a review first using the gh-pr-review skill."
- Check:
PR Number Extraction
Extract the PR number from user input:
- Pattern:
#?(\d+)(supports with or without#) - Examples: "#123" → 123, "PR 456" → 456, "pull request 789" → 789
- If no number found: "Error: Please provide a valid PR number (e.g., 'submit review for PR #123')."
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.
- 9d ago First seen · 544 lines · 20 tokens per session scan A 0531340b911c
gh-cr-submit is a skill published in the GitHub repository mir-am/skills-agents-ai-coding (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 4,098 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
git-workflow
Conventional commits, PR creation, and quality gate verification.
review-gate
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met.
hunk-extensions
Maps the hunkdiff/extension authoring surface for Hunk, the terminal diff viewer — hiding or reordering reviewed files, docked panes, alternate file views, commands and key bindings, dialogs, workspace writes, themes, syntax languages, VCS backends, lifecycle events. Use when writing, debugging, or installing a Hunk…
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.