record-a-test-result

record-a-test-result is a skill for Claude Code from Exponentially-Platform/Rapidly-MCP. It costs 97 tokens per session (380 once invoked), scanned A, original, MIT.

A tool for recording what happened in an idea experiment, such as a landing page, sign-up form, pre-order, pilot, or customer conversation. It stores the observations and gives advice on whether to continue, change, or stop.

In plain words
What is it for?
Use it to record how many people saw a test, how many took the intended action, the dates involved, unusual details, and the resulting recommendation.
Why use it?
It turns test results into a recorded decision instead of leaving them as informal impressions. Keeping results and corrections with the experiment makes the team's reasoning easier to review.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the rapidly plugin — 4 skills, 1 MCP server shipped together

Good fit Use it to record how many people saw a test, how many took the intended action, the dates involved, unusual details, and the resulting recommendation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/exponentially-platform/rapidly-mcp/record-a-test-result
Install

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.

Any agent
npx skills add Exponentially-Platform/Rapidly-MCP --skill record-a-test-result
Clone the repo
git clone --depth 1 https://github.com/Exponentially-Platform/Rapidly-MCP

Made for: Claude Code.

Or install rapidly, the plugin that ships this one along with the rest of its 4 skills, 1 MCP server.

Wrote 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.

agentmods badge for record-a-test-result

README.md
[![agentmods](https://agentmods.dev/badge/skills/exponentially-platform/rapidly-mcp/record-a-test-result/github.svg)](https://agentmods.dev/skills/exponentially-platform/rapidly-mcp/record-a-test-result)
Your own site
<a href="https://agentmods.dev/skills/exponentially-platform/rapidly-mcp/record-a-test-result"><img src="https://agentmods.dev/badge/skills/exponentially-platform/rapidly-mcp/record-a-test-result/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.

agentmods 80×15 button for record-a-test-result

Your own site · 80×15
<a href="https://agentmods.dev/skills/exponentially-platform/rapidly-mcp/record-a-test-result"><img src="https://agentmods.dev/badge/skills/exponentially-platform/rapidly-mcp/record-a-test-result.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 380 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00097 $0.00380
Opus 5.5 $0.00039 $0.00152
Sonnet 5.5 $0.00019 $0.00076
Haiku 4.5 $0.00010 $0.00038

Measured 13d ago against content hash 27fd48c436b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

record-a-test-result 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 13d 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.

plugins/rapidly/skills/record-a-test-result/SKILL.md · 24 lines

What it actually says

Record a test result and decide

A test only helps if the result is written down against the idea and someone makes a call. Rapidly keeps every observation and decision with the experiment, so the team can see why an idea moved forward or stopped.

Run it

  1. Find the idea. If the user gives a project ID or link, call get_idea. Otherwise call list_ideas and confirm which idea and experiment they mean.
  2. Get the facts of what happened: how many people saw the test, how many took the action, over what dates, and anything unusual. Ask for the numbers if the user only gives an impression.
  3. Call record_test_result with those observations for the right experiment. If a number was wrong earlier, record a correction rather than a new result.
  4. Call decide_idea to get Rapidly's advisory recommendation: continue, change or stop, with its reasoning.
  5. Show the user the result against the pass mark set before the test, Rapidly's recommendation and the reasoning.

What to tell the user

  • The recommendation is advice. The team decides, and Rapidly doesn't change the idea's stage on its own.
  • Record what customers did, not what they said they'd do.

Keep personal data about customers out of the observations. Counts and dates are enough.

Changes

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.

  1. 13d ago First seen · 24 lines · 97 tokens per session scan A 27fd48c436b3

Subscribe to this mod's changes

record-a-test-result is a skill published in the GitHub repository Exponentially-Platform/Rapidly-MCP (2 stars, last pushed 6d ago), licensed MIT. It adds 97 tokens to every session and 380 once invoked, about $0.0004 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-10-10.

Related

Other skills, from other repositories

featurevisor

Author, test, query and integrate Featurevisor feature flags, A/B experiments and remote configuration. Use in Featurevisor projects (featurevisor.config.js) for features, segments, attributes, global variables and compositions, conditions, rollouts, test specs and scenarios, datafiles, targets, Sets and promotions…

featurevisor/featurevisor · 131 tokens

researcher

Use when user wants to optimize or tune something measurable through repeated experiments — "make X faster", "improve [metric]", "find best config", "iterate overnight", "run experiments until it hits N". Triggers on quantitative goals (build time, latency, pass rate, accuracy) or qualitative ones scoreable against a…

krzysztofdudek/ResearcherSkill · 96 tokens

ab-testing

Use when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go significant. NOT recurring metric tracking (that is analytics), NOT north-star/KPI trees (that is kpi-framework), NOT projecting metrics…

ericrisco/rsc-harness · 79 tokens

A/B Test Validation

Validating A/B test implementations including traffic splitting accuracy, statistical significance calculation, metric tracking, and experiment cleanup.

PramodDutta/qaskills · 27 tokens

idea-os

Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with mermaid user journey and kill criteria.

skillmds/skillmd · 60 tokens

idea-check

Pre-build reality check. Scans GitHub, HN, npm, PyPI, and Stack Overflow for existing competitors before you build. Use when starting a new project, evaluating a side project idea, or doing a build-vs-buy decision.

mnemox-ai/idea-reality-mcp · 53 tokens