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 wataru-maeda/react-native-boilerplate --skill manage-prsgit clone --depth 1 https://github.com/wataru-maeda/react-native-boilerplateWrote 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/wataru-maeda/react-native-boilerplate/manage-prs)<a href="https://agentmods.dev/skills/wataru-maeda/react-native-boilerplate/manage-prs"><img src="https://agentmods.dev/badge/skills/wataru-maeda/react-native-boilerplate/manage-prs/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/wataru-maeda/react-native-boilerplate/manage-prs"><img src="https://agentmods.dev/badge/skills/wataru-maeda/react-native-boilerplate/manage-prs.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.00053 | $0.00540 |
| Opus 5.5 | $0.00021 | $0.00216 |
| Sonnet 5.5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
manage-prs 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.
What it actually says
Manage PRs
Follow Git rules. Work branches target dev. Promotion PRs go from dev to stg and from stg to main.
Actions
| Request | Read |
|---|---|
| Open a PR for the current branch | create.md |
| Review one or more PRs | review.md |
Promote dev → stg → main |
promote.md |
| Tag and publish a release | release.md |
PR Rules
Title
- Write
type(scope): description, at most 70 characters. Use the types and scopes in Commits. - Squash merges use the title as the commit message.
- Title promotion PRs
chore: promote dev to stgorchore: release v<version>forstgtomain.
Body
- Fill
.github/pull_request_template.mdfrom the actual diff and commits. Never reuse old text. - Link related issues in Overview with
Closes #N. - Tick only checks that ran. Record failures and skipped checks in Notes.
- Fill Test Cases with actual results, including Maestro flows and the platforms they ran on. Remove the table when there are none.
- Remove empty sections and placeholders. Leave screenshots to the user when UI changed.
Merge
- Merge only when asked and after required checks pass.
- Squash merge work branches into
dev. Use merge commits for promotion and hotfix merge-back PRs (Merge and Version). - Never pass
--subject. GitHub titles the commit<PR title> (#<N>), which links it back to the PR. - Keep work branches. Delete them only when cleanup is requested. Never delete
dev,stg, ormain.
gh pr checks <N> --watch
gh pr merge <N> --squash # work branches into dev
gh pr merge <N> --merge # dev → stg, stg → main, hotfix merge-back
What ships with it
4 files 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.
- today First seen · 47 lines · 53 tokens per session scan A 47d7f06971f3
manage-prs is a skill published in the GitHub repository wataru-maeda/react-native-boilerplate (519 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 540 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-10-19.
Other skills, from other repositories
react-native
Use when writing the JS/TS inside a React Native or Expo app — screens, Expo Router navigation, lists, Reanimated gestures, platform forks, offline state, native modules — or killing jank and render storms. NOT eas build/submit/OTA/config-plugin (that is expo), NOT a Dart app (that is flutter), NOT web React/DOM (that…
template-release
Cut a new template version — bump TEMPLATEVERSION, write upgrade notes, tag and publish a GitHub release. Use when releasing a new version of the agentic-mobile-blueprint template.
submitting-app-release
Runs pre-flight validation gates and submits the app to App Store Connect and Google Play Console via EAS CLI. Use when the user says "release", "submit to store", "publish", "deploy app", or "submit for review". Always runs release-checklist.js first — never submits past a failing gate without explicit user…
managing-app-versions
Manages semantic versioning for mobile apps across iOS and Android platforms. Use when the user says "bump version", "increment build number", "set version to", "release patch/minor/major", or "sync build numbers". Single source of truth is .msd/versions/{app-id}/version.json. Syncs to app.json (Expo), Info.plist…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…