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 ssmurfgg04-gif/context-m --skill experiment-suitegit clone --depth 1 https://github.com/ssmurfgg04-gif/context-mWrote 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/ssmurfgg04-gif/context-m/experiment-suite)<a href="https://agentmods.dev/skills/ssmurfgg04-gif/context-m/experiment-suite"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/experiment-suite/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/ssmurfgg04-gif/context-m/experiment-suite"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/experiment-suite.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.00048 | $0.02769 |
| Opus 5 | $0.00024 | $0.01385 |
| Sonnet 5 | $0.00010 | $0.00554 |
| Haiku 4.5 | $0.00005 | $0.00277 |
Grade A, and why
experiment-suite 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.
This is a copy
91% identical to experiment-suite — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experiment Suite
Overview
End-to-end experiment package builder. Single stage, full quality from the start. The agent (Claude Code / Cursor / Aider / Codex / …) writes everything directly using its own tools (Write, Bash, WebFetch, …). This skill contains procedure + reference playbooks + figure-example scripts — no Python runtime, no LLM SDK.
The substantive work is decomposed into reference playbooks under references/:
| Reference | Topic |
|---|---|
references/00-incremental-execution.md |
how to do this without losing work: batches, persistence, resume — read first |
references/01-design-depth.md |
what a real experiment design contains (motivation → hypothesis → datasets → baselines → metrics → ablations → budget) |
references/01a-data-contract.md |
runtime dataset binding: source, access route, version, split, and reuse boundary |
references/02-code-quality.md |
code-skeleton standards — runnable model.py, data.py, train.py, evaluate.py |
references/03-results-protocol.md |
results.json schema; measured / simulated / illustrative provenance |
references/04-publication-figures.md |
publication-grade charts, multi-panel layouts, taste rules |
references/04a-figure-contract.md |
figure logic before plotting: conclusion, panel map, reviewer risk |
references/04b-figure-qa.md |
export bundle, editable text, statistics and image-integrity QA |
references/05-report-structure.md |
structured experiment_report.md (problem → design → method → results → analysis → limitations) |
references/06-quality-gate.md |
self-check before delivery |
Also: figure_examples/ — publication-style matplotlib scripts plus a shared style kit the agent can use as starting points.
Read the relevant reference before writing, not after. The full pass does not fit in a single turn — references/00-incremental-execution.md is the only execution mode that completes.
When to Use
- User wants to "design an experiment" for a research question.
- User needs runnable code for a specific task (classification / forecasting / detection / …).
- User wants to compare methods and have a structured report at the end.
- User needs publication-quality figures of experimental results.
What ships with it
17 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.
- figure_examples/FIGURE_CONTRACT_TEMPLATE.md 249 B
- figure_examples/make_fig_02_horizon_sweep.py 1.3 KB runs code
- figure_examples/make_fig_03_heatmap.py 1.6 KB runs code
- figure_examples/make_fig_04_ablation.py 2.1 KB runs code
- figure_examples/README.md 1.3 KB
- figure_examples/requirements.txt 145 B
- figure_examples/style_kit.py 2.6 KB runs code
- references/00-incremental-execution.md 4.5 KB
- references/01-design-depth.md 5.9 KB
- references/01a-data-contract.md 3.0 KB
- references/02-code-quality.md 8.3 KB
- references/03-results-protocol.md 7.1 KB
- references/04-publication-figures.md 6.9 KB
- references/04a-figure-contract.md 1.6 KB
- references/04b-figure-qa.md 1.4 KB
- references/05-report-structure.md 5.7 KB
- references/06-quality-gate.md 6.3 KB
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 · 201 lines · 48 tokens per session scan A 44fffe0dfbfe
experiment-suite is a skill published in the GitHub repository ssmurfgg04-gif/context-m (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 2,769 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to experiment-suite, differing in 42 lines, and is treated as a copy.
Other skills, from other repositories
ai-style
A Chinese-language writing guide for producing or revising reader-facing text such as product announcements, public-account articles, emails, and README files. It focuses on reducing patterns that make writing sound machine-generated.
triage
A task-routing guide that identifies goals, dependencies, and acceptance conditions before work begins. It orders work as research, calculation or execution, and writing.
causal
Analyze cause-and-effect relationships in the Semantica knowledge graph — causal chains, interventions, counterfactuals, and causal influence scores.
coding
A coding guide for writing and running Python programs in a sandbox. It requires scripts to be small and reproducible, with their actual output or errors reported.
emem-field-tokens
Get a native-resolution raster field over an area from emem, or a field over time, as a signed, verifiable artifact rather than a set of per-cell scalars. Use when the user needs the actual grid of values over an area of interest (a world model input, an NDVI/band drape, change analysis over a scene window, exportable…
review-ticket
Review a Jira ticket during backlog grooming or refinement. Audits the ticket for testability, AC completeness, missing edge cases, and potential blockers. Outputs a structured review the SDT can bring to the grooming session. Use when: "review this ticket", "check ACs", "testability review", "grooming". Do NOT use…