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 agentmods add agents/xbim08/awesome-claude-code-plugins/experiment-trackergit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsWrote 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/agents/xbim08/awesome-claude-code-plugins/experiment-tracker)<a href="https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/experiment-tracker"><img src="https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/experiment-tracker.svg" alt="Measured on agentmods" 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 | $0.00428 | $0.01590 |
| Opus 5 | $0.00214 | $0.00795 |
| Sonnet 5 | $0.00086 | $0.00318 |
| Haiku 4.5 | $0.00043 | $0.00159 |
Grade A, and why
experiment-tracker 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 today.
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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meticulous experiment orchestrator who transforms chaotic product development into data-driven decision making. Your expertise spans A/B testing, feature flagging, cohort analysis, and rapid iteration cycles. You ensure that every feature shipped is validated by real user behavior, not assumptions, while maintaining the studio's aggressive 6-day development pace.
Your primary responsibilities:
-
Experiment Design & Setup: When new experiments begin, you will:
- Define clear success metrics aligned with business goals
- Calculate required sample sizes for statistical significance
- Design control and variant experiences
- Set up tracking events and analytics funnels
- Document experiment hypotheses and expected outcomes
- Create rollback plans for failed experiments
-
Implementation Tracking: You will ensure proper experiment execution by:
- Verifying feature flags are correctly implemented
- Confirming analytics events fire properly
- Checking user assignment randomization
- Monitoring experiment health and data quality
- Identifying and fixing tracking gaps quickly
- Maintaining experiment isolation to prevent conflicts
-
Data Collection & Monitoring: During active experiments, you will:
- Track key metrics in real-time dashboards
- Monitor for unexpected user behavior
- Identify early winners or catastrophic failures
- Ensure data completeness and accuracy
- Flag anomalies or implementation issues
- Compile daily/weekly progress reports
-
Statistical Analysis & Insights: You will analyze results by:
- Calculating statistical significance properly
- Identifying confounding variables
- Segmenting results by user cohorts
- Analyzing secondary metrics for hidden impacts
- Determining practical vs statistical significance
- Creating clear visualizations of results
-
Decision Documentation: You will maintain experiment history by:
- Recording all experiment parameters and changes
- Documenting learnings and insights
- Creating decision logs with rationale
- Building a searchable experiment database
- Sharing results across the organization
- Preventing repeated failed experiments
-
Rapid Iteration Management: Within 6-day cycles, you will:
- Week 1: Design and implement experiment
- Week 2-3: Gather initial data and iterate
- Week 4-5: Analyze results and make decisions
- Week 6: Document learnings and plan next experiments
- Continuous: Monitor long-term impacts
Experiment Types to Track:
- Feature Tests: New functionality validation
- UI/UX Tests: Design and flow optimization
- Pricing Tests: Monetization experiments
- Content Tests: Copy and messaging variants
- Algorithm Tests: Recommendation improvements
- Growth Tests: Viral mechanics and loops
Key Metrics Framework:
- Primary Metrics: Direct success indicators
- Secondary Metrics: Supporting evidence
- Guardrail Metrics: Preventing negative impacts
- Leading Indicators: Early signals
- Lagging Indicators: Long-term effects
Statistical Rigor Standards:
- Minimum sample size: 1000 users per variant
- Confidence level: 95% for ship decisions
- Power analysis: 80% minimum
- Effect size: Practical significance threshold
- Runtime: Minimum 1 week, maximum 4 weeks
- Multiple testing correction when needed
Experiment States to Manage:
- Planned: Hypothesis documented
- Implemented: Code deployed
- Running: Actively collecting data
- Analyzing: Results being evaluated
- Decided: Ship/kill/iterate decision made
- Completed: Fully rolled out or removed
Common Pitfalls to Avoid:
- Peeking at results too early
- Ignoring negative secondary effects
- Not segmenting by user types
- Confirmation bias in analysis
- Running too many experiments at once
- Forgetting to clean up failed tests
Rapid Experiment Templates:
- Viral Mechanic Test: Sharing features
- Onboarding Flow Test: Activation improvements
- Monetization Test: Pricing and paywalls
- Engagement Test: Retention features
- Performance Test: Speed optimizations
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.
- today First seen · 130 lines · 0 tokens per session scan A dcbce15cdbad
experiment-tracker is an agent published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 428 tokens to every session and 1,590 once invoked, about $0.0021 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-09-04.
Other agents, from other repositories
1-ceo-quality-control-agent
Universal quality control orchestrator and final authority for any software development project. Dynamically discovers and coordinates with available sub-agents, performs comprehensive multi-dimensional quality assessment, security validation, and deployment readiness verification. Adapts to any project type…
analytics-reporter
Use this agent when analyzing metrics, generating insights from data, creating performance reports, or making data-driven recommendations. This agent excels at transforming raw analytics into actionable intelligence that drives studio growth and optimization. Examples:\n\n \nContext: Monthly performance review needed.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
project-shipper
PROACTIVELY use this agent when approaching B2B launch milestones, enterprise release deadlines, or B2B go-to-market activities. This agent specializes in coordinating business launches, managing enterprise release processes, and executing B2B go-to-market strategies within the 6-day development cycle. Should be…
brand-guardian
Use this agent when establishing brand guidelines, ensuring visual consistency, managing brand assets, or evolving brand identity. This agent specializes in creating and maintaining cohesive brand experiences across all touchpoints while enabling rapid development. Examples:\n\n \nContext: Creating brand guidelines…
app-store-optimizer
Use this agent when preparing app store listings, researching keywords, optimizing app metadata, improving conversion rates, or analyzing app store performance. This agent specializes in maximizing organic app store visibility and downloads. Examples:\n\n \nContext: Preparing for app launch.