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 vibesurf-ai/claude-surf --skill summarygit clone --depth 1 https://github.com/vibesurf-ai/claude-surfWrote 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/vibesurf-ai/claude-surf/summary)<a href="https://agentmods.dev/skills/vibesurf-ai/claude-surf/summary"><img src="https://agentmods.dev/badge/skills/vibesurf-ai/claude-surf/summary/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/vibesurf-ai/claude-surf/summary"><img src="https://agentmods.dev/badge/skills/vibesurf-ai/claude-surf/summary.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.00026 | $0.00146 |
| Opus 5 | $0.00013 | $0.00073 |
| Sonnet 5 | $0.00005 | $0.00029 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
summary 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.
What it actually says
Summary - Webpage Summarization
Overview
AI-powered summarization of webpage content.
When to Use
- User asks what a page is about
- Need a quick summary of content
- Get main points from an article
- Understand page purpose
Available Actions
| Action | Description |
|---|---|
skill_summary |
Summarize a web page with tab_id |
How It Works
Call VibeSurf API with skill_summary on the current tab. Returns AI-generated summary of the page content.
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 First seen · 28 lines · 26 tokens per session scan A e3b12740dc2f
summary is a skill published in the GitHub repository vibesurf-ai/claude-surf (24 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 146 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-30.
Other skills, from other repositories
moai-platform-chrome-extension
Chrome Extension Manifest V3 development specialist covering service workers, content scripts, message passing, chrome. APIs, side panel, declarativeNetRequest, and Chrome Web Store publishing. Use when building browser extensions.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
browser-tools
Security wrapper over the upstream agent-browser skill, adding URL blocklisting, rate limiting, robots.txt enforcement, and scraping guardrails. Use when automating browser workflows that need safety limits.
browser-automation-agent
Automate web browsers for AI agents using agent-browser CLI with deterministic element selection.
using-web-scraping
Search and scrape public web content with headless Chrome and DuckDuckGo using safe practices.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.