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 bobberrisford/affiliatemcp --skill affiliate-network-setup-helpgit clone --depth 1 https://github.com/bobberrisford/affiliatemcpWrote 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/bobberrisford/affiliatemcp/affiliate-network-setup-help)<a href="https://agentmods.dev/skills/bobberrisford/affiliatemcp/affiliate-network-setup-help"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/affiliate-network-setup-help/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/bobberrisford/affiliatemcp/affiliate-network-setup-help"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/affiliate-network-setup-help.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.00069 | $0.01272 |
| Opus 5 | $0.00034 | $0.00636 |
| Sonnet 5 | $0.00014 | $0.00254 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
affiliate-network-setup-help 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating instructions
You are walking a publisher through credential acquisition for one named affiliate network. This is a conversational skill — expect follow-ups. Be patient and precise.
Supported networks
This server ships adapters for many affiliate networks. affiliate_list_networks is the authoritative list of adapters registered in this server — call it rather than relying on a fixed set. It does not prove that the user has configured credentials. This skill carries detailed, hand-written setup walkthroughs for the four launch networks (awin, cj, impact, rakuten); every other registered network is set up the same way through its docs/networks/<slug>.md guide and the adapter's setupSteps() (Step 2 and Step 3 below). If the user names a network affiliate_list_networks does not return, say the server has no registered adapter for it and stop.
Step 1 — identify the network
The user usually names it. If they describe it indirectly ("the one I use for Amazon"), map it to a network slug and confirm against affiliate_list_networks rather than assuming. If they hesitate between two networks, ask which dashboard they currently log into. When credential state matters, use affiliate_run_diagnostic or recommend affiliate-networks-mcp doctor <slug> rather than inferring it from affiliate_list_networks.
Step 2 — read the setup doc
The canonical source per network is docs/networks/<slug>.md in this repo (e.g. docs/networks/awin.md, docs/networks/cj.md, etc.). These docs walk through:
- Where to sign up (if relevant).
- Where in the dashboard the credential lives (exact menu path and UI labels).
- How long approval typically takes.
- Which environment variables this server expects (e.g.
AWIN_API_TOKEN,AWIN_PUBLISHER_ID).
Read the file, then quote the relevant section back. Do not paraphrase UI labels — the dashboard's wording is the user's anchor.
Step 3 — fallback if the doc is missing
If docs/networks/<slug>.md does not exist (this can happen in early dev), fall back to the adapter's own setupSteps(). The information is the same shape — field, label, description, example — and is the authoritative list of what the wizard collects. You can surface this by suggesting the user run affiliate-networks-mcp setup and walking through what each prompt will ask for, based on the adapter's setup steps. Hand-written quick references for the four launch networks follow; for any other network, read its setupSteps() (or docs/networks/<slug>.md) directly rather than guessing:
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.
- 12d ago First seen · 66 lines · 69 tokens per session scan A fcff1ba63e5f
affiliate-network-setup-help is a skill published in the GitHub repository bobberrisford/affiliatemcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 1,272 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
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…
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.
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…
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…