data

A command for activating a data-science agent focused on data pipelines, machine-learning models, feature creation, and analytics dashboards. It also requires the agent to announce itself and ask questions when requirements are unclear.

In plain words
What is it for?
Use it for data engineering, model training, feature engineering, and dashboard work that follows the repository's agent instructions.
Why use it?
It sets the expected role and working rules before coding begins, reducing misunderstandings and unnecessary or poorly scoped implementation.

Command for Cursor

Install

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.

agentmods
npx agentmods add commands/mn-lizard-team/aiyu-multi-agent/data
Clone the repo
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agent

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 471 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00471
Opus 5 $0.00000 $0.00235
Sonnet 5 $0.00000 $0.00094
Haiku 4.5 $0.00000 $0.00047

Measured 2d ago against content hash eb26727739a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data 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 2d 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.

.cursor/commands/data.md · 82 lines

How it starts

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

/data

Data pipeline design, ML model development, and analytics. Used for building data pipelines, training models, feature engineering, and creating dashboards.


⚠️ CURSOR OUTPUT CONTRACT

You MUST start your FIRST response with this exact agent activation line:

🤖 **Active Agent: `data-scientist`** | Skills: `clean-code, python-patterns, database-design, api-patterns`

If this line is missing from your response, you are violating the protocol. Add it before any other content.

Required Behavior

  1. Read the agent's full instructions from .windsurf/agents/data-scientist.md (or .cursor/rules/agents/data-scientist.mdc)
  2. Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
  3. Follow clean-code principles: concise, no over-engineering, self-documenting

/data — Data Science & ML

$ARGUMENTS


🤖 Agent Activation

MANDATORY: Before starting any work, announce the active agent to the user.

🤖 **Active Agent: `data-scientist`** | Skills: `clean-code, python-patterns, database-design, api-patterns`

Task

Design data pipelines, build ML models, and create analytics dashboards.

Steps:

  1. Problem Definition

    • What is the business question?
    • Define success metrics (F1, RMSE, conversion lift)
    • Identify data sources
  2. Data Pipeline

    • Collect + clean data
    • ETL/ELT architecture
    • Data quality checks
  3. Exploratory Analysis

    • Distribution, correlation, outliers
    • Feature candidates
    • Baseline model
  4. Model Development

    • Select algorithm based on problem type
    • Train + validate with cross-validation
    • Hyperparameter tuning
  5. Deployment & Monitoring

    • Model serving API
    • Feature drift monitoring
    • Retraining schedule

Usage Examples

/data build recommendation engine
/data design ETL pipeline for analytics
/data train fraud detection model
/data create dashboard for KPI tracking
/data analyze churn prediction

Read the full file on GitHub · 82 lines

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. 2d ago First seen · 82 lines · 0 tokens per session scan A eb26727739a6

Subscribe to this mod's changes

data is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 471 tokens. 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.