grovs-campaigns

grovs-campaigns is a skill for Claude Code from grovs-io/mcp. It costs 63 tokens per session (544 once invoked), scanned A, original, MIT.

A campaign manager for Grovs deep links. A campaign is a group of links whose views, opens, installs, and revenue can be measured together.

In plain words
What is it for?
Use it to create campaigns, attach links to them, list campaigns by performance, review combined metrics, and archive old campaigns.
Why use it?
It makes it easier to organize related marketing links and assess an entire marketing effort instead of reviewing each link separately.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grovs plugin — 6 skills, 1 MCP server shipped together

Good fit Use it to create campaigns, attach links to them, list campaigns by performance, review combined metrics, and archive old campaigns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/grovs-io/mcp/grovs-campaigns
Install

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.

Any agent
npx skills add grovs-io/mcp --skill grovs-campaigns
Clone the repo
git clone --depth 1 https://github.com/grovs-io/mcp

Made for: Claude Code.

Or install grovs, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

Wrote 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.

agentmods badge for grovs-campaigns

README.md
[![agentmods](https://agentmods.dev/badge/skills/grovs-io/mcp/grovs-campaigns/github.svg)](https://agentmods.dev/skills/grovs-io/mcp/grovs-campaigns)
Your own site
<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.

agentmods 80×15 button for grovs-campaigns

Your own site · 80×15
<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>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 7b964ce2e067, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

plugin/skills/grovs-campaigns/SKILL.md · 46 lines

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_campaign deactivates all links permanently. Always confirm with the user.
  • No "get single campaign." Use list_campaigns with term: "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_campaigns with sort_by: "revenue" or sort_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.

Changes

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.

  1. 9d ago First seen · 46 lines · 63 tokens per session scan A 7b964ce2e067

Subscribe to this mod's changes

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.

Related

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.

luna-prompts/skillnote · 54 tokens

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.

ZengLiangYi/ChatCrystal · 54 tokens

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".

luna-prompts/skillnote · 39 tokens

verify

Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.

yha9806/academic-writing-toolkit · 26 tokens

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…

ulises-jeremias/agent-toolkit · 96 tokens

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.

ulises-jeremias/agent-toolkit · 64 tokens