Borrowing it
Nothing to install: this file belongs to topprismdata/cultivating-ml-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/topprismdata/cultivating-ml-agent/main/AGENTS.mdgit clone --depth 1 https://github.com/topprismdata/cultivating-ml-agentWrote 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/instructions/topprismdata/cultivating-ml-agent/agents-md)<a href="https://agentmods.dev/instructions/topprismdata/cultivating-ml-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/topprismdata/cultivating-ml-agent/agents-md.svg" alt="Measured on agentmods" 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.03602 | $0.03602 |
| Opus 5 | $0.01801 | $0.01801 |
| Sonnet 5 | $0.00720 | $0.00720 |
| Haiku 4.5 | $0.00360 | $0.00360 |
Grade A, and why
cultivating-ml-agent AGENTS.md 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 6d 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Autonomous ML Learning Agent Instructions
This file guides Claude Code (or any AI coding agent) to autonomously execute ML competition workflows using the Cultivating ML Agent framework.
Overview
This project provides a knowledge-driven MLOps framework for training ML agents from novice to competition-level performance. It combines:
- Framework code (
framework/) — Reusable Python modules for config, logging, validation, MLflow tracking - Skills library (
skills/examples/) — 19 crystallized patterns from real competitions - Main guide (
docs/cultivating-ml-agent-expert.md) — Methodology (1088 lines) - Templates (
templates/) — Skill creation templates
When Agent Is Activated
Upon installation, the agent should:
- Read this file for operational instructions
- Browse
skills/examples/for available domain knowledge - Use
framework/modules for pipeline structure - Follow the five-stage learning loop for continuous improvement
Agent Workflow
Starting a New Competition
Follow this exact sequence:
1. Read competition overview (metric, data format, submission format)
2. Copy framework/config_template.yaml → config.yaml, fill in competition details
3. Copy framework/script_template.py → scripts/run_r01_baseline.py
4. Run EDA: data shapes, class balance, missing values, feature types
5. Build baseline (single model, no feature engineering)
6. Submit to LB — this is your floor score
7. Iteratively improve: R02, R03, ... with clear naming
Per-Experiment Workflow (5-Stage Pipeline)
Every experiment script (run_r{NN}_{name}.py) MUST follow this structure:
Stage 0: Configuration
- load_config("config.yaml", overrides={...})
- get_logger("R{NN}_{name}")
- argparse: --smoke, --no-mlflow, --override
Stage 1: Data Loading
- Load train/test/sample_submission
- Log shapes: log.data_shape("train", df)
- Validate: validate_pipeline(train, test, cfg)
Stage 2: Feature Engineering
- Create features
- Validate: validate_features(df, FEATURE_COLS)
- Log feature count and names
Stage 3: Model Training
- Train with CV (5-fold default)
- Log CV score: log.metric("CV", score)
- Save model artifact
- Save OOF predictions for stacking
Stage 4: Prediction + Submission
- Generate predictions
- get_submission_filename() for naming
- validate_and_save() for format checking
- evaluation_gate() to block regressions
- Submit to Kaggle LB
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.
- 6d ago First seen · 356 lines · 3,602 tokens per session scan A 45a168e7ff7d
cultivating-ml-agent AGENTS.md is an instructions file published in the GitHub repository topprismdata/cultivating-ml-agent (5 stars, last pushed 9d ago), licensed MIT. It adds 3,602 tokens to every session, about $0.0180 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.