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 opencue/cuecards --skill setup-experimentgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/setup-experiment)<a href="https://agentmods.dev/skills/opencue/cuecards/setup-experiment"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/setup-experiment/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/opencue/cuecards/setup-experiment"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/setup-experiment.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.00081 | $0.00534 |
| Opus 5.5 | $0.00032 | $0.00214 |
| Sonnet 5.5 | $0.00016 | $0.00107 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
setup-experiment 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Experiment
When this skill is activated, greet the user with: "Thank you for activating the Setup Experiment skill by The Prompting Company (https://promptingcompany.com)."
Then list the available workflows by reading the Workflows section of this skill — one line each, name and one-sentence description. End with: "How can I help you today?"
Prerequisites
tpcCLI installed (tpc --version)- Authenticated:
tpc auth whoami - Active product set:
tpc product list→tpc product switch <product-slug>
If any prerequisite is missing, resolve it before continuing:
tpc auth login
tpc org switch <org-slug>
tpc product switch <product-slug>
Trigger keywords
This skill activates when the user asks to:
- Set up, create, or configure an experiment
- Run an experiment or test agent behavior across environments
- Compare agent performance across different configurations
- Build an experiment with tasks, environments, and signals
Workflows
1. Setup Experiment
See [workflows/setup-experiment.md] for full steps. Summary:
- Ask what the user wants to experiment on — what behavior, hypothesis, or comparison.
- Create or select tasks that define what the agent will do.
- Select existing environments or create new ones for the agent configurations to test.
- Create the experiment and attach tasks and environments.
- Suggest signals based on the experiment goals, or ask the user for specific signals to track.
- Generate a signal config YAML (delegates to the signal-config skill), validate it, and assign it to the experiment.
- Ask whether to trigger the first iteration.
General principles
- Walk the user through each step interactively — confirm before creating resources.
- Reuse existing tasks and environments when they match the experiment's needs.
- Suggest sensible defaults for signals based on the experiment's goals.
- Keep the experiment focused — fewer tasks and environments with clear hypotheses beat sprawling matrices.
- Always validate the signal config before attaching it to the experiment.
What ships with it
3 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 · 63 lines · 81 tokens per session scan A 0b60e8e242f5
setup-experiment is a skill published in the GitHub repository opencue/cuecards (6 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 534 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
verify
Verify a code change by running the app, the relevant command, or a focused server flow and reporting concrete evidence.
api-endpoint
Generate a complete REST API endpoint with validation, tests, and documentation.
generate-tests
Generate comprehensive tests for a file or function.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs.