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 awin-apply-to-programmesgit 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/awin-apply-to-programmes)<a href="https://agentmods.dev/skills/bobberrisford/affiliatemcp/awin-apply-to-programmes"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/awin-apply-to-programmes/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/awin-apply-to-programmes"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/awin-apply-to-programmes.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.00157 | $0.02549 |
| Opus 5 | $0.00078 | $0.01274 |
| Sonnet 5 | $0.00031 | $0.00510 |
| Haiku 4.5 | $0.00016 | $0.00255 |
Grade A, and why
awin-apply-to-programmes 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 11d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating instructions
You take a set of Awin programmes the publisher has not yet joined and apply to each, in an assisted batch. The joinable set is read from the Awin API. The application itself is a click Awin gives no API for, so it happens in the operator's own authenticated Awin session through Claude-in-Chrome. For every programme you surface the advertiser's terms, let the operator review and drop rows, and submit only after one explicit confirmation of the whole batch. That single confirmation is the operator's informed acceptance of the terms you showed, and nothing else.
This skill is assisted, not unattended. It never accepts terms the operator has not seen, never invents a programme or a term, and never records a result the browser consumer did not observe at the verify target. If a programme's terms cannot be shown, or anything unexpected appears at submit time, it stops on that programme and hands back rather than guessing.
This is the doing half of the Awin publisher-application workflow. To discover
and rank which brands to apply to first, use brand-application-shortlist; bring
its shortlist here to apply.
Step 1 — read the joinable programmes from the API
Read the joinable set from the API, never the dashboard:
Call affiliate_awin_list_programmes({ status: "available" }). On the Awin
publisher adapter this maps to Awin's relationship=notjoined, so it returns
programmes the publisher can apply to but has not joined. Each row is a
Programme with id (the advertiser id), name, commissionRate,
categories, and currency.
State plainly that the API is the verified source of what is joinable and that the browser is used later only for the application click Awin exposes no API for. If the call fails, surface the verbatim envelope (network, operation, message, httpStatus) and stop. Never treat a failure as an empty set.
If the operator already has a shortlist (for example from
brand-application-shortlist), keep only its programmes that still appear in this
joinable set. Drop any that are no longer joinable and say which, so you never try
to apply to something already joined, pending, or rejected.
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.
- 11d ago First seen · 210 lines · 157 tokens per session scan A 23318aacbabe
awin-apply-to-programmes is a skill published in the GitHub repository bobberrisford/affiliatemcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 157 tokens to every session and 2,549 once invoked, about $0.0008 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…
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…
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…