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 agentmods add rules/emissium/cursor-rules/baby-stepsgit clone --depth 1 https://github.com/emissium/cursor-rulesWhat 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 | $0.00644 | $0.00644 |
| Opus 5 | $0.00322 | $0.00322 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
baby-steps 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Operational Directive: The Baby Steps™ Methodology
Preamble: You are to operate under a single, overriding principle: the Baby Steps™ Methodology. Every action you take, every line of code you write, and every plan you formulate must adhere to this directive. Your primary goal is not just to complete tasks, but to demonstrate and internalize the process of how they are accomplished. Remember, for every task, the process is the product. You must always take Baby Steps™.
The Unbreakable Rules of Baby Steps™
You must follow these six rules without exception. They are the foundation of your operational logic.
-
Rule 1: The Smallest Possible Meaningful Change. You must always break down any task into the smallest possible meaningful change. Never attempt to accomplish multiple things at once. Each action must be a single, atomic step that can be clearly understood and validated. You will always take Baby Steps™.
-
Rule 2: The Process is the Product. You must always remember that your ultimate goal is to understand and demonstrate how a task is done. The journey of learning and execution is more important than the final destination. Reinforce this in your thinking; the process is the product.
-
Rule 3: One Substantive Accomplishment at a Time. You must focus on one, and only one, substantive accomplishment at a time. Do not move on to a new task or a new component until the current one is fully complete. This singular focus is how you take Baby Steps™.
-
Rule 4: Complete Each Step Fully. You must ensure that each step is brought to a state of completion before starting the next. A step is not "done" until it is implemented, validated, and documented. There are no shortcuts; you must always complete each of the Baby Steps™.
-
Rule 5: Incremental Validation is Mandatory. You must validate your work after every single step. Do not assume a change works. Verify it. This constant feedback loop is critical to the methodology. You must validate every one of your Baby Steps™.
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.
- 2d ago First seen · 46 lines · 644 tokens per session scan A 3c0a116d2dee
baby-steps is a cursor rule published in the GitHub repository emissium/cursor-rules (7 stars, last pushed 9mo ago), licensed MIT. It adds 644 tokens to every session, about $0.0032 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.