Borrowing it
Nothing to install: this file belongs to swimmwatch/cloakbrowser-mcp. 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/swimmwatch/cloakbrowser-mcp/main/.agents/skills/project-pull-request/SKILL.mdgit clone --depth 1 https://github.com/swimmwatch/cloakbrowser-mcpWrote 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/swimmwatch/cloakbrowser-mcp/project-pull-request)<a href="https://agentmods.dev/skills/swimmwatch/cloakbrowser-mcp/project-pull-request"><img src="https://agentmods.dev/badge/skills/swimmwatch/cloakbrowser-mcp/project-pull-request/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/swimmwatch/cloakbrowser-mcp/project-pull-request"><img src="https://agentmods.dev/badge/skills/swimmwatch/cloakbrowser-mcp/project-pull-request.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.00083 | $0.00966 |
| Opus 5.5 | $0.00033 | $0.00386 |
| Sonnet 5.5 | $0.00017 | $0.00193 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
project-pull-request 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 10d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Pull Request
Use this skill for cloakbrowser-mcp Pull Request work. The repository's
.github/PULL_REQUEST_TEMPLATE.md is the required PR body format; do not
replace it with a second template.
Authorization
- A request to review or prepare a PR does not authorize edits, commits, pushes, PR creation/update, readiness changes, merge, or branch deletion.
- Before each external mutation, confirm that the user explicitly authorized
that action. Use Codex's standard Request User Input tool
(
request_user_input) for any unresolved material base, head, assignee, readiness, scope, or execution choice. Follow the tool's exposed schema and host constraints; permission requests use the host's approval process. - Never infer push or PR authorization from approval of code, a specification, a plan, local checks, or a commit.
- Preserve unrelated worktree changes and stage only the intended PR scope.
Preconditions
- Inspect
git status, current branch, upstream tracking, and diff before creating or updating a PR. - Do not open a PR from
main. - Use
mainas the base branch unless the user explicitly gives another base. - Before creating a commit for the PR, open and scan
https://www.conventionalcommits.org/en/v1.0.0/. - Obtain explicit commit authorization before creating the commit.
- Run
npm run checklocally after the final edits and before creating a commit. If it fails, fix the failure or report the blocker; do not commit. - If any file changes after
npm run check, rerunnpm run checkbefore committing. - After explicit push authorization, push the current feature branch to
originbefore creating the PR. - Run
npm run checkagain on the committed branch before pushing. If it fails, fix the failure or report the blocker; do not push or create/update the PR. - Create PRs ready for review by default. Use draft only when the user explicitly asks for a draft PR.
Assignee
- Assign the PR to the authenticated GitHub user by default. Resolve the login
with
gh api user --jq .loginor the equivalent GitHub connector identity. - For this repository, the expected default assignee is
swimmwatchunless the user explicitly requests another assignee. - If the assignee cannot be resolved or GitHub rejects it, report the blocker and leave the PR otherwise complete.
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.
- 10d ago Changed · +3 lines 122942d89d9b
- 2mo ago First seen · 89 lines · 83 tokens per session scan A f45ef9280dd9
project-pull-request is a skill published in the GitHub repository swimmwatch/cloakbrowser-mcp (173 stars, last pushed 5d ago), licensed MIT. It adds 83 tokens to every session and 966 once invoked, about $0.0003 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
cl-link-from-hash
Use this skill to get a link to a Gerrit Changelist (CL) from a given commit hash in the Chromium repository. Use when you need to find the review discussion, comments, or related issues for a specific commit. Don't use for linking to files or code lines.
Review Changes
Review or explain the code changes in a working tree or branch, grouped by severity, with file and line references and an architecture diagram of what the change does.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
prismer-github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
address-review
Read PR review comments from GitHub, evaluate, address, and reply.
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.