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/ifokeev/airbrowser-mcp/prnpx skills add ifokeev/airbrowser-mcp --skill prgit clone --depth 1 https://github.com/ifokeev/airbrowser-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/ifokeev/airbrowser-mcp/pr)<a href="https://agentmods.dev/skills/ifokeev/airbrowser-mcp/pr"><img src="https://agentmods.dev/badge/skills/ifokeev/airbrowser-mcp/pr.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.00028 | $0.00777 |
| Opus 5 | $0.00014 | $0.00388 |
| Sonnet 5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Create pull requests with conventional commit-style titles using the gh CLI. Never add co-author labels.
Title Format
<type>(<scope>): <subject>
Same types and scopes as conventional commits — see /commit skill for the full list.
Keep titles under 72 characters. Use the description for details, not the title.
Rules
- No co-author labels — never add
Co-Authored-Bylines anywhere - Title follows conventional commit format: imperative mood, lowercase, no period
- Description uses the structured template below
- Always push the branch before creating the PR
- Base branch defaults to
masterunless specified otherwise
Steps
-
Check the current branch and understand the scope of changes:
git branch --show-current git status git log --oneline master..HEAD git diff master...HEAD --stat -
If on
master— you cannot push directly. Create a new branch first:git checkout -b <type>/<short-description>Branch naming:
feat/add-report-notifications,fix/cron-duplicate,chore/bump-ui-kit, etc. If there are uncommitted changes, they will carry over to the new branch. -
If the branch has not been pushed yet:
git push -u origin HEAD -
Analyze all commits on the branch (not just the latest) to draft the title and summary
-
Create the PR using a HEREDOC for the body:
gh pr create --title "type(scope): subject line here" --body "$(cat <<'EOF' ## Summary - Brief bullet points explaining the changes ## Test plan - [ ] How to verify these changes work EOF )" -
Return the PR URL to the user
Description Template
## Summary
- 1-3 bullet points describing what changed and why
## Test plan
- [ ] Steps or checks to verify the changes
Keep it concise. No fluff, no emojis, no generated-by footers.
Examples
Title examples:
feat(console-ui): add scheduled report notifications
fix(console-server): prevent duplicate cron triggers
refactor(cloud-router): extract auth middleware into module
chore: bump ui-kit to v0.15.0 across packages
fix(ai-engineer): handle streaming timeout on large contexts
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 · 113 lines · 28 tokens per session scan A 688d8605ca74
pr is a skill published in the GitHub repository ifokeev/airbrowser-mcp (9 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 777 once invoked, about $0.0001 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-31.
Other skills, from other repositories
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
deep-x-research
Deep, exhaustive research on a topic across X (Twitter) by driving Grok (x.com/i/grok) through surf. Use when the user wants comprehensive X research on a concept, technique, trend, tool, or creator scene; needs categorized findings with every claim traceable to post URLs; or when a single Grok query is not enough.
surf-codebase
Navigate and modify surf-cli codebase - Chrome extension + native host for AI browser automation. Use for surf-cli code work, architecture questions, implementing browser control/CDP/accessibility/network features.
build-plugin
Complete plugin development workflow: build, test, icon, troubleshoot, and setup. Use when the user wants to build a plugin, create a plugin, troubleshoot issues, add icons, or install/configure plugins. Triggers on: build plugin, create plugin, develop plugin, new plugin, plugin icon, troubleshoot, debug, setup…
bump-version
Bump package versions across all platform packages and plugins in lockstep. Use when the user wants to bump versions, update versions, or prepare a release. Triggers on: bump version, bump versions, version bump, update version, prepare release.
ralph
Plan work and generate ralph task files for autonomous execution. Use when the user wants to plan tasks, create a prd, run ralph, or fix a batch of issues. Triggers on: ralph, create tasks, plan this, run ralph, prd.