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 1024XEngineer/bytemind --skill github-prgit clone --depth 1 https://github.com/1024XEngineer/bytemindWrote 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/1024xengineer/bytemind/github-pr)<a href="https://agentmods.dev/skills/1024xengineer/bytemind/github-pr"><img src="https://agentmods.dev/badge/skills/1024xengineer/bytemind/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/1024xengineer/bytemind/github-pr"><img src="https://agentmods.dev/badge/skills/1024xengineer/bytemind/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.00017 | $0.00132 |
| Opus 5.5 | $0.00007 | $0.00053 |
| Sonnet 5.5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00002 | $0.00013 |
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 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
- Confirm comparison baseline (base ref and feature ref).
- Summarize major file and module changes.
- Mark behavior-change, edge-case, and compatibility risks.
- Map review comments to actionable response plans.
- Provide a pre-merge verification checklist.
Output Contract
- Diff Summary
- Key Risks
- Review Comment Response Plan
- Pre-merge Verification Checklist
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 24 lines · 17 tokens per session scan A d560631f07ec
github-pr is a skill published in the GitHub repository 1024XEngineer/bytemind (27 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 132 once invoked, about $0.0001 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
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
doris-repo-review
Review an Apache Doris PR from a local clone with the same multi-agent, shared-ledger convergence workflow as the CI Code Review Runner. Use when the user supplies a PR to /doris-repo-review, asks to review a Doris PR locally, or asks for the CI-style review flow. Safely align only the current worktree to the exact PR…
armada-pr
PR-first finish for a feature lane. Use before reporting a feature done. Triggers on: PR, finish feature, gh pr create, merge, lane complete.
code-review
Systematic code review SOP covering correctness, security, performance, and maintainability — plus GitHub PR review workflow (diff, inline comments, approve via gh/REST).
review
Self-review code before pushing. Use when the user wants to check their changes, asks 'anything I missed', says 'ready to push', or wants a pre-PR sanity check.
review
Review current uncommitted git changes with full file context and produce a structured report with severity levels, actionable fixes, and an approval verdict.