Borrowing it
Nothing to install: this file belongs to usk6666/yorishiro-proxy. 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/usk6666/yorishiro-proxy/main/.claude/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/usk6666/yorishiro-proxyWrote 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/usk6666/yorishiro-proxy/pr)<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/pr"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/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/usk6666/yorishiro-proxy/pr"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/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.00015 | $0.00587 |
| Opus 5.5 | $0.00006 | $0.00235 |
| Sonnet 5.5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr
A skill for creating Pull Requests.
Steps
- Build verification: Run
make buildand confirm no errors - Run tests: Run
make testand confirm all tests pass - Review diff: Check changes with
git diff main...HEAD - Generate PR title: Create a title in Conventional Commits format (
feat(scope): description) - Generate PR body: Generate body including a summary of changes and test plan
- Create PR: Run
gh pr create --title "<title>" --body "<body>" - Display result: Show the PR URL
PR Body Template
## Summary
- <bulleted list of changes>
## Test plan
- [ ] Test items
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Notes
- If build or tests fail, do not create the PR and report the problem instead
- Default base branch is
main
Stacked PRs
When PR B is stacked on PR A's branch (B.base == A.head_branch) and you merge PR A with gh pr merge --delete-branch, GitHub auto-closes PR B because its base branch no longer exists. Auto-closed PRs cannot be reopened (gh pr reopen returns "Could not open the pull request") nor have their base changed (gh pr edit --base returns "Cannot change the base branch of a closed pull request").
Two safe sequences:
-
Retarget before merging upstream (preferred when you have time):
gh pr edit <B> --base <A's base> # B will temporarily show A's diff too — fine if A merges first gh pr merge <A> --squash --admin --delete-branch -
Recreate downstream after merging upstream:
gh pr merge <A> --squash --admin --delete-branch # closes B # in a worktree on B's branch: git rebase --onto origin/<base> <A's-original-head-commit> # drops A's commits, replays only B's git push --force-with-lease gh pr create --base <base> --head <B's-branch>
Do not use --delete-branch on the upstream PR if the downstream has not been retargeted — you lose the PR thread (closed PRs are still readable but lose OPEN semantics for review-gate and merge-queue tooling).
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 · 59 lines · 15 tokens per session scan A 9bbec1dc1a1e
pr is a skill published in the GitHub repository usk6666/yorishiro-proxy (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 587 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
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
github-via-nyxid
Operate a user's GitHub account through NyxID's credential-brokering proxy (service slug api-github) — read and write repositories, files, issues, pull requests, commits, branches, Actions, gists and anything else the GitHub REST API exposes, all on the user's behalf and without ever handling a raw token. NyxID…
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
git-workflow
Git best practices for version control and collaboration.
p4-workspace-setup
P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools. Use when: creating workspaces, configuring client specs, syncing files, switching workspaces, or checking workspace status in P4.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.