Borrowing it
Nothing to install: this file belongs to geosp/mcp-mixsearch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/geosp/mcp-mixsearch/main/.agents/skills/github-pr/SKILL.mdgit clone --depth 1 https://github.com/geosp/mcp-mixsearchWrote 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/geosp/mcp-mixsearch/github-pr)<a href="https://agentmods.dev/skills/geosp/mcp-mixsearch/github-pr"><img src="https://agentmods.dev/badge/skills/geosp/mcp-mixsearch/github-pr/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/geosp/mcp-mixsearch/github-pr"><img src="https://agentmods.dev/badge/skills/geosp/mcp-mixsearch/github-pr.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.00094 | $0.01546 |
| Opus 5.5 | $0.00038 | $0.00618 |
| Sonnet 5.5 | $0.00019 | $0.00309 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
github-pr 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 today.
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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub pull request
Work is tracked in GitHub issues and delivered through pull requests into the default branch (main). Follow the branch, commit and attribution rules in AGENTS.md throughout.
Step 1 - Check the repository and the base branch
- Find the base branch:
gh repo view --json defaultBranchRef -q .defaultBranchRef.name. If that fails (no remote or noghauth), usemain. - Run
git remote -v. If there is no remote, say so: you can still prepare the description (Steps 2-6), but pushing and creating the PR in Step 7 are unavailable until the repository exists.
Step 2 - Get to a clean feature branch
Run git status (including untracked files) and check the current branch.
If the current branch is the base branch, the work was done without a feature branch:
- If there are unstaged or untracked changes, stash them (
git stash --include-untracked). - Update the base branch (
git pull) if a remote exists. - Create a feature branch that follows the branch naming in
AGENTS.md:<type>/<issue>-<slug>. If you don't know the issue number, go to Step 3 first. - If changes were stashed, pop them (
git stash pop).
If there are unstaged or untracked changes (on any branch):
- Show the user a summary of the changes and ask whether they belong in this PR. If not, stop and let the user sort them out.
- Stage and commit them with clear, descriptive messages. Prefer several small commits when the changes are logically distinct. No attribution: no
Co-Authored-Bytrailers, no "Generated with ..." lines, and no agent as author (AGENTS.md).
Never commit secrets, .env files, pr-description.md, or project data that AGENTS.md keeps out of Git.
Step 3 - Identify the GitHub issue
Look for the issue number, in this order:
- The branch name (
feat/3-input-validation->#3). - The commit messages (
git log <base>..HEAD). - Ask the user.
When you have a number, read the issue: gh issue view <n> --json number,title,body,labels,milestone,state. Use its acceptance criteria and linked plan as context.
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.
- today First seen · 114 lines · 94 tokens per session scan A 72db9284a5bd
github-pr is a skill published in the GitHub repository geosp/mcp-mixsearch (0 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 1,546 once invoked, about $0.0004 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-11-18.
github-pr compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| github-prgeosp/mcp-mixsearch | Skill | 0 | yesterday | MIT | A | 94 | Claude Code, Codex |
| prYeachan-Heo/oh-my-claudecode | Skill | 41k | today | MIT | A | 47 | Claude Code |
| merge-batchdiegosouzapw/OmniRoute | Skill | 88k | 3d ago | MIT | A | 46 | Claude Code |
| otto-pr-review-loopomnigent-ai/omnigent | Skill | 11k | today | Apache-2.0 | A | 17 | Claude Code, Codex |
| engram-branch-prGentleman-Programming/engram | Skill | 8.2k | yesterday | MIT | A | 37 | Claude Code, Codex |
| github-contributordaymade/claude-code-skills | Skill | 1.5k | today | MIT | A | 105 | Claude Code, Codex |
| revdiffumputun/revdiff | Skill | 961 | today | MIT | A | 253 | Claude Code |