vertical-benchmark-pack

vertical-benchmark-pack is a skill for Claude Code from bobberrisford/affiliatemcp. It costs 80 tokens per session (432 once invoked), scanned A, original, MIT.

A comparison of one affiliate programme with other managed brands in the same business category. It compares commission, partner mix, reversals, and average order value, then identifies gaps.

In plain words
What is it for?
Benchmarking a brand against confirmed category peers and finding practical areas for improvement.
Why use it?
A programme's figures are hard to judge without comparable peers. This shows where the target brand is above, near, or below the peer midpoint.

Skill for Claude Code

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

Part of the affiliate-networks-mcp plugin — 37 skills, 1 MCP server shipped together

Good fit Benchmarking a brand against confirmed category peers and finding practical areas for improvement.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bobberrisford/affiliatemcp/vertical-benchmark-pack
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 bobberrisford/affiliatemcp --skill vertical-benchmark-pack
Clone the repo
git clone --depth 1 https://github.com/bobberrisford/affiliatemcp

Made for: Claude Code.

Or install affiliate-networks-mcp, the plugin that ships this one along with the rest of its 37 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 vertical-benchmark-pack

README.md
[![agentmods](https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/vertical-benchmark-pack/github.svg)](https://agentmods.dev/skills/bobberrisford/affiliatemcp/vertical-benchmark-pack)
Your own site
<a href="https://agentmods.dev/skills/bobberrisford/affiliatemcp/vertical-benchmark-pack"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/vertical-benchmark-pack/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 vertical-benchmark-pack

Your own site · 80×15
<a href="https://agentmods.dev/skills/bobberrisford/affiliatemcp/vertical-benchmark-pack"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/vertical-benchmark-pack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 432 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.00080 $0.00432
Opus 5 $0.00040 $0.00216
Sonnet 5 $0.00016 $0.00086
Haiku 4.5 $0.00008 $0.00043

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

Security

Grade A, and why

vertical-benchmark-pack 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 12d 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.

premium-skills/vertical-benchmark-pack/SKILL.md · 46 lines

What it actually says

Vertical benchmark

You are benchmarking one target brand against the other brands the agency manages in the same vertical. Only compare brands the user confirms share a vertical — never assume a category. Never invent figures.

Step 1 — define the peer set

Ask the user for the target brand and which of the managed brands count as its vertical peers. Resolve bindings with affiliate_resolve_brand. Agree the period (default last 90 days).

Step 2 — pull comparable metrics

For the target and each peer, across their networks, call affiliate_<network>_get_programme_performance, affiliate_<network>_get_earnings_summary, and affiliate_<network>_list_transactions.

Step 3 — compare like for like

Build a table with one row per brand:

  • commission rate / effective commission where available;
  • reversal rate;
  • average order value;
  • partner count and top-partner concentration.

Mark the target's position (above / at / below the peer median) on each metric, quoting the target figure and the peer median.

Step 4 — gap list

List where the target trails its peers, most material first, each with the two figures behind it, and a suggested action (e.g. review commission, recruit in an under-covered partner type). Matter-of-fact, UK spelling.

Constraints

  • Peers are user-confirmed, same vertical, same agency book only.
  • Keep currencies separate; do not invent FX.
  • Quote both the target and the peer benchmark for every gap.
  • Surface failed reads; never fill a gap with a zero.
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. 12d ago First seen · 46 lines · 80 tokens per session scan A 9d408d1a42e0

Subscribe to this mod's changes

vertical-benchmark-pack is a skill published in the GitHub repository bobberrisford/affiliatemcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 432 once invoked, about $0.0004 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens