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/commitnpx skills add ifokeev/airbrowser-mcp --skill commitgit clone --depth 1 https://github.com/ifokeev/airbrowser-mcpWhat 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.00021 | $0.00569 |
| Opus 5 | $0.00010 | $0.00284 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
commit 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 yesterday.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commit
Create conventional commit messages following the Conventional Commits specification. Never add co-author labels.
Format
<type>(<scope>): <subject>
<body>
Types
| Type | Purpose |
|---|---|
feat |
New feature |
fix |
Bug fix |
refactor |
Code restructuring (no behavior change) |
docs |
Documentation only |
style |
Formatting, whitespace (no code change) |
test |
Adding or fixing tests |
chore |
Build, CI, tooling, dependencies |
perf |
Performance improvement |
Scope (optional)
Use the affected package or module as scope, matching this repo's conventions. Common scopes:
- Package names:
console-ui,console-server,cloud-router,ai-engineer,sheets-ui - Subsystems:
billing,scheduler,auth,mcp - Use the scope from recent commits when in doubt — run
git log --oneline -20to check
Rules
- No co-author labels — never add
Co-Authored-Bylines - Subject line: imperative mood, lowercase, no period, max 72 chars
- Body: explain why, not what. Wrap at 80 chars
- One logical change per commit — split unrelated changes
- Match the project's existing commit style (check recent history)
Steps
- Run
git statusandgit diff --cachedto see staged changes - If nothing is staged, stage the relevant files (prefer specific files over
git add -A) - Analyze the changes and determine the appropriate type and scope
- Draft a concise commit message
- Create the commit using a HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF' type(scope): subject line here Optional body explaining why this change was made. EOF )" - Run
git statusafter to verify
Examples
feat(console-ui): add group chat with realtime subscriptions
fix(console-server): correct next_run calculation for scheduled reports
refactor(cloud-router): merge mcp server into main binary
chore: update ui-kit to v0.15.0 across packages
fix(ai-engineer): handle token limit exceeded in streaming response
perf(billing): batch usage dimension writes to reduce DB round-trips
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.
- yesterday First seen · 81 lines · 21 tokens per session scan A 28d1d05f5a6a
commit is a skill published in the GitHub repository ifokeev/airbrowser-mcp (9 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 569 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.