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 client-weekly-reportgit 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/client-weekly-report)<a href="https://agentmods.dev/skills/bobberrisford/affiliatemcp/client-weekly-report"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/client-weekly-report/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/client-weekly-report"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/client-weekly-report.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.00117 | $0.01303 |
| Opus 5 | $0.00059 | $0.00651 |
| Sonnet 5 | $0.00023 | $0.00261 |
| Haiku 4.5 | $0.00012 | $0.00130 |
Grade A, and why
client-weekly-report 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Premium scope note
The free programme-performance-report skill already produces the weekly
client note for one named brand: a short, pasteable verdict, a headline
table, and top risers/fallers. This premium skill does not change that
profile's content or its rules; it adds two things:
- Batching: run the weekly-client-note profile for every registered brand in the book in one pass, instead of the operator asking brand by brand.
- Voice-matched, send-ready formatting: apply each brand's recorded
strategy voice, audience, and escalation threshold (from
affiliate_get_client_strategy) to its own note, and format every note as a ready-to-paste email draft with a consistent subject-line convention, so a Monday morning produces N send-ready drafts rather than N separate conversations.
It is not a headline-only rollup (that is the free agency-portfolio-rollup
skill, or this pack's portfolio-rollup); it produces the actual
per-client narrative text.
Assumptions and requirements
- At least one brand is registered via
affiliate_resolve_brand. If none are, stop and point the user ataffiliate-networks-mcp setup. - Credentials for bound networks are configured; recommend
affiliate-networks-mcp doctor <slug>when credential state is uncertain. - Client strategy files are optional per brand. A brand with no recorded strategy still gets a note, in a neutral default voice, with no escalation threshold applied.
- This produces email-ready drafts, never sends them. Sending is a separate action outside any tool this skill uses.
Step 1 — enumerate the book
Call affiliate_resolve_brand with no arguments. The response is an array of
{ brand, network, networkBrandId }. Group by brand to get the book's
distinct client list. If empty, tell the user no brands are registered and
stop.
Step 2 — load each brand's plan
Call affiliate_list_client_strategies once. For each brand with
hasStrategy or hasKpi, call
affiliate_get_client_strategy({ brand }) to load its strategy prose (for
voice, audience, and escalation threshold) and kpi.targets (for the
verdict). Brands with neither are noted as "no recorded voice; using the
default weekly-note format" and proceed without a custom voice.
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 · 119 lines · 117 tokens per session scan A e2520b4fb384
client-weekly-report is a skill published in the GitHub repository bobberrisford/affiliatemcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 1,303 once invoked, about $0.0006 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…