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 agentmods add skills/swimmwatch/cloakbrowser-mcp/project-pull-requestnpx skills add swimmwatch/cloakbrowser-mcp --skill project-pull-requestgit 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.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.00931 |
| Opus 5 | $0.00042 | $0.00465 |
| Sonnet 5 | $0.00017 | $0.00186 |
| Haiku 4.5 | $0.00008 | $0.00093 |
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 5d 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 — 89 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 the global Prompt MCP for any unresolved material base, head, assignee, readiness, scope, or execution choice.
- 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.
- 5d 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 (56 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 931 once invoked, about $0.0004 per session on Opus 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
browser-search
Multi-engine web search (SearXNG) + browsing/scraping (Camofox, CloakBrowser). Use whenever you need to do web research.
chrome-orchestrator
Teach agents how to orchestrate Arthur and Gloria headless Chrome environments dynamically via the Python SDK and CLI.
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.