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 growsurf/growsurf-mcp --skill growsurf-agent-toolkitgit clone --depth 1 https://github.com/growsurf/growsurf-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/growsurf/growsurf-mcp/growsurf-agent-toolkit)<a href="https://agentmods.dev/skills/growsurf/growsurf-mcp/growsurf-agent-toolkit"><img src="https://agentmods.dev/badge/skills/growsurf/growsurf-mcp/growsurf-agent-toolkit/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/growsurf/growsurf-mcp/growsurf-agent-toolkit"><img src="https://agentmods.dev/badge/skills/growsurf/growsurf-mcp/growsurf-agent-toolkit.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.00090 | $0.01931 |
| Opus 5 | $0.00045 | $0.00966 |
| Sonnet 5 | $0.00018 | $0.00386 |
| Haiku 4.5 | $0.00009 | $0.00193 |
Grade A, and why
growsurf-agent-toolkit 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 8d 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.
GrowSurf Agent Toolkit
Use this skill to turn a user goal into a real GrowSurf program, not just API calls. Prefer the GrowSurf MCP tools when available; otherwise use the REST v2 API with the same order and checks.
Ground Rules
- Use the user's own GrowSurf API key. If they do not have an account, call
growsurf_create_account, give them the verification step, and pause until the key is usable. - If the user wants to work on an existing program and did not provide a
campaignId, callgrowsurf_list_campaignsfirst and pick or confirm the target program. - If the user wants to inspect or operate on an existing participant and did not provide a participant ID/email, call
growsurf_list_participantsfirst. - After
growsurf_create_campaign, pass the returnedidascampaignIdto every campaign-scoped tool. Do not rely on a process-level default after creating a new program. - Campaign create seeds type-specific starter content across Design, Emails, Options, Installation, rewards, and the GrowSurf Window. Fetch and review it before patching. Preserve starter content unless the user asks for a specific change.
- Treat starter content as the default source for Window copy, referred-friend copy, email copy, share settings, landing-page content, and rewards. Do not rebuild the program from scratch unless the user asks for a custom program.
- Keep rewards conservative until the user confirms money movement, payout funding, tax collection, and approval settings.
- Fetch before patching large config surfaces. Use
growsurf_get_campaign_design,growsurf_get_campaign_emails,growsurf_get_campaign_options, orgrowsurf_get_campaign_installation, then patch only the fields that must change. - Finish by proving what changed: fetch the campaign, key configs, and rewards again. Review the returned settings before reporting back.
- Ask for screenshot proof only when the work changes or installs a browser-visible GrowSurf flow. Skip that ask for read-only lookups, config summaries, and server-only API tasks. If the user wants GrowSurf preview screenshots, call
growsurf_capture_referral_flow_screenshotsand inspect the returned referrer Window and referred-friend images. If they want proof of their own installed site, use the host agent's browser automation tool, such as Playwright or a built-in browser tool, against the real installed page. Do not substitute a mock page unless the real page is unavailable, and say so if that happens.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 113 lines · 90 tokens per session scan A 17237218d2b7
growsurf-agent-toolkit is a skill published in the GitHub repository growsurf/growsurf-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 1,931 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…