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 Zfinix/aster --skill gh-pr-workflowgit clone --depth 1 https://github.com/Zfinix/asterWrote 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/zfinix/aster/gh-pr-workflow)<a href="https://agentmods.dev/skills/zfinix/aster/gh-pr-workflow"><img src="https://agentmods.dev/badge/skills/zfinix/aster/gh-pr-workflow/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/zfinix/aster/gh-pr-workflow"><img src="https://agentmods.dev/badge/skills/zfinix/aster/gh-pr-workflow.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.00046 | $0.00462 |
| Opus 5.5 | $0.00018 | $0.00185 |
| Sonnet 5.5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
gh-pr-workflow 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 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.
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.
What it actually says
GitHub PR workflow
- Use
ghfor GitHub operations. Structured queries beat scraping:gh pr view 12 --json title,body,files,comments,gh pr checks 12,gh issue list --limit 10. - Big diffs go to a file, not the conversation.
gh pr diff 12 > /tmp/pr12.diff, then search and read slices of that file. Never print a whole PR diff into the chat. - Draft first, post on approval. Write the review or comment body to a
scratch file, show it to the user, and only after they approve post it:
gh api repos/{owner}/{repo}/pulls/12/reviews --method POST --input review.json. Never post to GitHub as a side effect of being asked to "review". - One PR at a time, one comment per issue found. Do not batch several PRs' feedback into one pass, and do not stack multiple problems into one comment.
- Auth errors are a full stop. A 401 or
gh auth statusfailure means tell the user to rungh auth login. Retrying, or switching to raw git pushes, will not help. - PR bodies: summary plus test plan. Short paragraphs over prose walls. No attribution footers unless asked.
- Know which subcommands write. Reads (
view,list,diff,checks,apiGET,search) run freely; writes (create,edit,merge,close,comment,review, any--method POST/PATCH/PUT/DELETE,pr checkout,release create) change state and will ask the user for approval. Batch reads first, then propose the writes as one step instead of interleaving.
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 Changed · +5 lines 717f6035201b
- 1mo ago First seen · 26 lines · 46 tokens per session scan A eae7b3106da4
gh-pr-workflow is a skill published in the GitHub repository Zfinix/aster (131 stars, last pushed 2d ago), licensed Apache-2.0. It adds 46 tokens to every session and 462 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-08-30.
Other skills, from other repositories
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.