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 hoavdc/CodexKit --skill codexkit-a-b-test-plannergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-a-b-test-planner)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-a-b-test-planner"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-a-b-test-planner/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/hoavdc/codexkit/codexkit-a-b-test-planner"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-a-b-test-planner.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.00062 | $0.01366 |
| Opus 5.5 | $0.00025 | $0.00546 |
| Sonnet 5.5 | $0.00012 | $0.00273 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
codexkit-a-b-test-planner 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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A/B Test Planner
When to Use
- Before running any product experiment or feature test
- When optimizing conversion funnels or UX flows
- When leadership requires statistical rigor for feature decisions
- When planning multi-variant tests or sequential experiments
Procedure
Step 1 — Hypothesis
Write a clear, falsifiable hypothesis:
- If [change we're making]
- Then [metric we expect to change]
- Because [reasoning / user insight]
Step 2 — Metrics
| Type | Metric | Current Baseline |
|---|---|---|
| Primary | The metric that determines success | [value] |
| Secondary | Supporting metrics that provide context | [value] |
| Guardrail | Metrics that must NOT degrade | [value] |
Step 3 — Sample Size & Duration
Calculate required sample size using:
- Baseline conversion rate (p₁)
- Minimum Detectable Effect (MDE) — smallest meaningful change
- Statistical significance level (α) — typically 0.05
- Statistical power (1−β) — typically 0.80
n = f(p₁, MDE, α, β) → use standard sample size calculator
Duration = n / (daily traffic × allocation %)
Step 4 — Randomization Plan
- Randomization unit: user, session, device, or account
- Allocation: 50/50, or asymmetric with justification
- Stratification: any segments to balance (geography, plan, device)
- Exclusion: users to exclude (employees, bots, existing tests)
Step 5 — Decision Rules
| Outcome | Criteria | Action |
|---|---|---|
| Winner | Primary metric ↑ ≥ MDE, p < 0.05, guardrails stable | Ship to 100% |
| Neutral | No significant difference | Keep control, iterate hypothesis |
| Loser | Primary metric ↓ significantly | Revert, analyze why |
| Guardrail breach | Any guardrail metric degrades > threshold | Stop test immediately |
Step 6 — Rollout Playbook
- Ramp: 5% → 25% → 50% → 100% over [days]
- Monitoring: check metrics daily during ramp
- Rollback trigger: guardrail breach or unexpected anomaly
What ships with it
4 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.
- 1mo ago First seen · 167 lines · 62 tokens per session scan A d7d9039d7dde
codexkit-a-b-test-planner is a skill published in the GitHub repository hoavdc/CodexKit (26 stars, last pushed 13d ago), licensed MIT. It adds 62 tokens to every session and 1,366 once invoked, about $0.0002 per session on Opus 5.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
promo-video-pipeline
A workflow for producing promotional videos with Remotion, a React-based tool that renders video from code. It splits a storyboard into scenes, assigns work to separate agents, combines the results, and checks the actual rendered video.
verification-loop
Evidence-before-assertions workflow. Use before claiming work is done, before release, and after any behavior change in scripts/skills/MCP.
debug-hub
Evidence-first debugging WITH MCP tools. Use when debughub MCP server is available. Inject log calls, collect via HTTP API (port 39200), analyze through MCP tools, clean up when done. If debughub MCP is unavailable, use debug skill (bundled Python collector) instead.
reducing-aigc-detection
A rewriting workflow for lowering the likelihood that academic writing is labelled as AI-generated by detection services, while keeping formatting and footnotes.
architecting-security
A security-architecture guide for modeling threats and designing identity, access, privacy, and compliance controls. It covers approaches such as STRIDE, zero trust, single sign-on, multi-factor authentication, and GDPR-related privacy work.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…