experiment-log

experiment-log is a skill for Claude Code, Codex from zakelfassi/skills-driven-development. It costs 54 tokens per session (960 once invoked), scanned A, original, MIT.

A structured record of a machine-learning training run, including its settings, results, saved model files, and data version. An experiment ledger is a table or log used to compare these runs later.

In plain words
What is it for?
Use it after a training run or when comparing models, recording parameters, metrics, run IDs, artifact paths, source revision, and dataset version.
Why use it?
It makes it possible to identify exactly how a model was trained and compare its results before choosing one to promote.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/compare-runs.py --metric auc --top 5.

Good fit Use it after a training run or when comparing models, recording parameters, metrics, run IDs, artifact paths, source revision, and dataset version.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/zakelfassi/skills-driven-development
agentmods
npx agentmods add skills/zakelfassi/skills-driven-development/experiment-log

Made for: Claude Code, Codex.

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 experiment-log

README.md
[![agentmods](https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/experiment-log/github.svg)](https://agentmods.dev/skills/zakelfassi/skills-driven-development/experiment-log)
Your own site
<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/experiment-log"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/experiment-log/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 experiment-log

Your own site · 80×15
<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/experiment-log"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/experiment-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 960 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.00054 $0.00960
Opus 5.5 $0.00022 $0.00384
Sonnet 5.5 $0.00011 $0.00192
Haiku 4.5 $0.00005 $0.00096

Measured 1mo ago against content hash 4ec240bd91ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

experiment-log 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/log-experiment.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

examples/data-pipeline/skills/experiment-log/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Experiment Log

Record a training run's parameters, metrics, and artifact paths in the experiments ledger.

Inputs

  • Experiment name (e.g., churn-v3-lgbm)
  • Run ID (auto-generated if omitted: {name}-{YYYYMMDD-HHmmss})
  • Parameters (key-value pairs, e.g., learning_rate=0.05 n_estimators=500)
  • Metrics (key-value pairs, e.g., auc=0.83 f1=0.71 precision=0.79 recall=0.64)
  • Artifact path (model checkpoint, serialized pipeline, etc.)
  • Notes (free-form, optional)

Steps

  1. Collect run metadata

    import datetime, hashlib, json, os
    
    run_id = "{name}-" + datetime.datetime.utcnow().strftime("%Y%m%d-%H%M%S")
    git_sha = os.popen("git rev-parse --short HEAD").read().strip()
    dataset_version = open("data/.version").read().strip()  # semver or hash
    
  2. Capture parameters and metrics If using a training script that outputs JSON:

    python train.py --config config/{name}.yaml --output-metrics /tmp/metrics.json
    

    Otherwise, capture values directly from the trainer object:

    params = model.get_params()
    metrics = {"auc": roc_auc_score(y_test, y_pred), "f1": f1_score(y_test, y_pred)}
    
  3. Save artifacts

    import joblib
    artifact_path = f"artifacts/{run_id}/model.pkl"
    os.makedirs(os.path.dirname(artifact_path), exist_ok=True)
    joblib.dump(model, artifact_path)
    
  4. Append to the experiments ledger

    scripts/log-experiment.sh \
      --name "{name}" \
      --run-id "{run_id}" \
      --params '{"learning_rate": 0.05}' \
      --metrics '{"auc": 0.83, "f1": 0.71}' \
      --artifact "{artifact_path}" \
      --notes "{notes}"
    

    The ledger is experiments/log.csv — a flat CSV with one row per run.

  5. Verify the entry

    tail -n 5 experiments/log.csv
    

    Confirm: run_id is unique, metrics are numeric, artifact path exists.

  6. Compare with previous runs (optional)

    python scripts/compare-runs.py --metric auc --top 5
    

Read the full file on GitHub · 92 lines

Files

What ships with it

1 file 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.

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. 1mo ago First seen · 92 lines · 54 tokens per session scan A 4ec240bd91ed

Subscribe to this mod's changes

experiment-log is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 960 once invoked, about $0.0002 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-08-30.

Related

Other skills, from other repositories

agent-platform-tuning

Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).

google/skills · 64 tokens

agent-platform-model-registry

Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.

google/skills · 60 tokens

agent-platform-prompt-management

Manages and orchestrates prompts in Agent Platform. Use when you need to create, list, retrieve, version, or delete managed prompts in Agent Platform. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform prompts.

google/skills · 55 tokens

agent-platform-rag-engine-management

Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…

google/skills · 85 tokens

gke-inference

Deploys and optimizes AI/ML inference workloads on GKE, using GPUs, TPUs, and model servers. Use when deploying GKE inference servers, configuring GKE GPU resources for inference, or deploying LLMs on GKE. Don't use for migrating existing AI workloads to GKE (use google-cloud-solution-guided-gke-ai-migration), GKE RAG…

google/skills · 119 tokens

agent-platform-endpoint-management

Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model…

google/skills · 64 tokens