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 agency-portfolio-deepdivegit 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/agency-portfolio-deepdive)<a href="https://agentmods.dev/skills/bobberrisford/affiliatemcp/agency-portfolio-deepdive"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/agency-portfolio-deepdive/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/agency-portfolio-deepdive"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/agency-portfolio-deepdive.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.00086 | $0.00463 |
| Opus 5 | $0.00043 | $0.00231 |
| Sonnet 5 | $0.00017 | $0.00093 |
| Haiku 4.5 | $0.00009 | $0.00046 |
Grade A, and why
agency-portfolio-deepdive 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.
What it actually says
Agency portfolio deep dive
You are analysing the agency's entire book — every bound brand, every network — to surface structural risk and opportunity a headline rollup misses. Produce a ranked, evidence-backed view. Never invent figures.
Step 1 — enumerate the book
List every bound brand and its network bindings (affiliate_resolve_brand,
affiliate_list_networks). Agree the period with the user (default last 90
days).
Step 2 — pull per brand, per network
For each brand/network pair, call affiliate_<network>_get_earnings_summary,
affiliate_<network>_get_programme_performance, and
affiliate_<network>_list_transactions.
Step 3 — analyse structure
- Revenue concentration: share of total from the top brand, top network, and top partner. Flag anything over 40% as concentration risk.
- Partner overlap: partners that appear across multiple brands — where a single partner's change would move several brands at once.
- Reversal outliers: brand/network pairs with a reversal rate more than double the portfolio median (quote both).
- Single points of failure: brands whose revenue depends >60% on one partner or one network.
Step 4 — output
A ranked risk list (most material first), each item with the exact figures behind it, then two or three portfolio-level recommendations. Keep currencies separate. Matter-of-fact, UK spelling.
Constraints
- Evidence for every claim: quote the numbers, name the brand/network/partner.
- Never normalise currencies unless the user asks.
- Surface failed reads; a missing brand is a gap to flag, not a zero.
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 · 44 lines · 86 tokens per session scan A e52843045b01
agency-portfolio-deepdive is a skill published in the GitHub repository bobberrisford/affiliatemcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 463 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.
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…