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.
git clone --depth 1 https://github.com/dominodatalab/domino-claude-pluginWrote 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/commands/dominodatalab/domino-claude-plugin/domino-experiment-setup)<a href="https://agentmods.dev/commands/dominodatalab/domino-claude-plugin/domino-experiment-setup"><img src="https://agentmods.dev/badge/commands/dominodatalab/domino-claude-plugin/domino-experiment-setup/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/commands/dominodatalab/domino-claude-plugin/domino-experiment-setup"><img src="https://agentmods.dev/badge/commands/dominodatalab/domino-claude-plugin/domino-experiment-setup.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.00020 | $0.01213 |
| Opus 5 | $0.00010 | $0.00607 |
| Sonnet 5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
domino-experiment-setup 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 11d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/domino-experiment-setup Command
Set up MLflow experiment tracking for traditional machine learning projects in Domino.
Usage
/domino-experiment-setup [experiment_name]
What This Command Does
- Creates experiment setup code with unique naming
- Configures auto-logging for detected frameworks
- Adds Domino context as MLflow tags
- Creates example training script with best practices
Output
experiment_setup.py
"""
Domino Experiment Tracking Setup
Generated by /domino-experiment-setup
"""
import mlflow
import os
def setup_experiment(base_name: str = "experiment"):
"""
Set up a Domino-compatible MLflow experiment.
IMPORTANT: Experiment names must be unique across the entire
Domino deployment. This function appends username and project
to ensure uniqueness.
"""
username = os.environ.get('DOMINO_STARTING_USERNAME', 'unknown')
project = os.environ.get('DOMINO_PROJECT_NAME', 'unknown')
# Create unique experiment name
experiment_name = f"{base_name}-{project}-{username}"
mlflow.set_experiment(experiment_name)
print(f"Experiment set: {experiment_name}")
return experiment_name
def log_domino_context():
"""Log Domino environment information as tags."""
mlflow.set_tags({
"domino.user": os.environ.get('DOMINO_STARTING_USERNAME', 'unknown'),
"domino.project": os.environ.get('DOMINO_PROJECT_NAME', 'unknown'),
"domino.run_id": os.environ.get('DOMINO_RUN_ID', 'unknown'),
"domino.hardware_tier": os.environ.get('DOMINO_HARDWARE_TIER_NAME', 'unknown'),
})
# Auto-detect and enable framework logging
def setup_autolog():
"""Enable auto-logging for detected ML frameworks."""
try:
import sklearn
mlflow.sklearn.autolog()
print("Enabled sklearn auto-logging")
except ImportError:
pass
try:
import tensorflow
mlflow.tensorflow.autolog()
print("Enabled TensorFlow auto-logging")
except ImportError:
pass
try:
import torch
mlflow.pytorch.autolog()
print("Enabled PyTorch auto-logging")
except ImportError:
pass
try:
import xgboost
mlflow.xgboost.autolog()
print("Enabled XGBoost auto-logging")
except ImportError:
pass
try:
import lightgbm
mlflow.lightgbm.autolog()
print("Enabled LightGBM auto-logging")
except ImportError:
pass
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.
- 11d ago First seen · 202 lines · 20 tokens per session scan A 76e917df2b82
domino-experiment-setup is a command published in the GitHub repository dominodatalab/domino-claude-plugin (6 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 1,213 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.