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 grovs-io/mcp --skill grovs-campaignsgit clone --depth 1 https://github.com/grovs-io/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/grovs-io/mcp/grovs-campaigns)<a href="https://agentmods.dev/skills/grovs-io/mcp/grovs-campaigns"><img src="https://agentmods.dev/badge/skills/grovs-io/mcp/grovs-campaigns/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/grovs-io/mcp/grovs-campaigns"><img src="https://agentmods.dev/badge/skills/grovs-io/mcp/grovs-campaigns.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.00063 | $0.00544 |
| Opus 5 | $0.00032 | $0.00272 |
| Sonnet 5 | $0.00013 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
grovs-campaigns 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 9d 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
Grovs: Manage Campaigns
What a campaign is
A grouping of links — nothing more. No config, no settings. You create it, attach links via campaign_id, then list_campaigns shows aggregated metrics (views, opens, installs, revenue) across all links in that campaign.
Hard limitations
- No rename. Name is permanent.
- No unarchive.
archive_campaigndeactivates all links permanently. Always confirm with the user. - No "get single campaign." Use
list_campaignswithterm: "name"to find one. - No delete without archive. Archive is the only way to remove.
Typical workflow
create_campaign(project_id: "p_m9f", name: "Summer Sale 2026") → campaign_id: 42
create_link(project_id: "p_m9f", name: "Banner Ad", campaign_id: 42)
create_link(project_id: "p_m9f", name: "Email CTA", campaign_id: 42)
...later...
list_campaigns(project_id: "p_m9f", sort_by: "revenue") → see all campaigns ranked
Pagination
list_campaigns paginates — returns meta.page, meta.total_pages. If user says "show more," call again with page: current + 1 using the same filters.
When to suggest campaigns proactively
- User is about to create 2+ related links → "Want to group these in a campaign so you can track them together?"
- User asks "which campaign is doing best" →
list_campaignswithsort_by: "revenue"orsort_by: "installs" - User wants a link-level breakdown within a campaign → use
search_links(shows per-link metrics) — there's no campaign-scoped link search, so search by tag or name pattern
If something fails
- "Campaign not found" on archive → campaign_id is a number, not a string. Check you're passing the numeric ID from
list_campaigns.
All tool responses are pre-formatted
Every Grovs tool returns human-readable formatted text. Don't reformat — just present and add context.
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.
- 9d ago First seen · 46 lines · 63 tokens per session scan A 7b964ce2e067
grovs-campaigns is a skill published in the GitHub repository grovs-io/mcp (2 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 544 once invoked, about $0.0003 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
skillnote
Self-hosted skill registry for OpenClaw. Stores procedures your team writes (name, description, body), syncs them to disk before each task, and collects which-helped/which-failed signals from the agent so the registry improves over time.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.