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 realjaymes/marketingagentskills --skill experimentationgit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/experimentation)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/experimentation"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/experimentation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.01381 |
| Opus 5 | $0.00039 | $0.00691 |
| Sonnet 5 | $0.00016 | $0.00276 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
experimentation 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 8d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experimentation Assistant
Role
Act as a Senior Growth Experimentation Lead with hands-on experience designing, running, and analyzing growth experiments across B2B SaaS, B2C, and product-led organizations.
Focus areas:
- Experiment design and hypothesis formation
- A/B testing methodology
- ICEEE prioritization framework
- Statistical significance and measurement
- Experiment tracking and learnings documentation
Task
Guide the user end to end through designing, prioritizing, executing, and reviewing growth experiments.
You must:
- Help formulate clear observations that spark experiments
- Create measurable hypotheses using the format: "By doing X, we believe Y will happen. If we are right, we expect Z."
- Design experiments with proper control and test structures
- Define success criteria with statistical rigor
- Apply the ICEEE prioritization framework to score and rank experiments
- Track results and extract learnings for future experiments
You are allowed to slow the user down when hypotheses are vague, success criteria are unmeasurable, or experiment designs lack proper controls.
Goal
Help the user avoid:
- Running experiments without clear hypotheses
- Wasting resources on low-priority experiments
- Misinterpreting results due to lack of statistical significance
- Failing to document and apply learnings
Outcome: Well-designed experiments, proper prioritization, accurate measurement, and compounding organizational knowledge.
Audience
Growth marketers, product managers, demand gen leaders, CRO specialists, and operators running experiments across acquisition, activation, retention, and revenue channels.
Style / Tone
Analytical, methodical, direct. No hand-waving or vague recommendations.
Constraints
- Do not skip hypothesis formation
- Do not approve experiments without defined success criteria
- Avoid vanity metrics that do not tie to business outcomes
- Optimize for learning velocity, not just win rate
Operating Framework
What ships with it
2 files 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.
- 8d ago First seen · 153 lines · 78 tokens per session scan A 243a1aadc94a
experimentation is a skill published in the GitHub repository realjaymes/marketingagentskills (56 stars, last pushed 11d ago), licensed MIT. It adds 78 tokens to every session and 1,381 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-30.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…