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/nedcodes-ok/cursorrules-collection/tensorflowgit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWrote 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/rules/nedcodes-ok/cursorrules-collection/tensorflow)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/tensorflow"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/tensorflow.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 | $0.00413 | $0.00413 |
| Opus 5 | $0.00206 | $0.00206 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
tensorflow 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 yesterday.
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.
What it actually says
TensorFlow Rules
Model Building
- Use tf.keras.Model or Sequential for model architecture
- Define layers in init, forward pass in call() method
- Use Input layer to define input shape explicitly
- Implement custom layers by inheriting tf.keras.layers.Layer
- Use functional API for complex model architectures
Data Pipeline
- Use tf.data.Dataset for efficient data loading
- Apply transformations with map(), filter(), and batch()
- Use tf.data.AUTOTUNE for optimal performance
- Implement proper data augmentation in pipeline
- Use tf.data.experimental.AUTOTUNE for num_parallel_calls
Training Configuration
- Configure mixed precision with policy = tf.keras.mixed_precision.Policy('mixed_float16')
- Use appropriate optimizers (Adam, AdamW, SGD) with learning rate schedules
- Implement callbacks for checkpointing, early stopping, and monitoring
- Use tf.keras.utils.plot_model for architecture visualization
- Configure proper loss functions and metrics
Memory & Performance
- Use tf.function decorator for graph compilation
- Avoid Python loops in graph mode operations
- Use tf.GradientTape for custom training loops
- Implement gradient clipping for training stability
- Use tf.distribute.Strategy for multi-GPU training
Model Persistence
- Save models with model.save() for complete model persistence
- Use SavedModel format for production deployment
- Export models to TensorFlow Lite for mobile/edge deployment
- Implement versioning strategy for model management
- Use TensorFlow Serving for production inference
Best Practices
- Set random seeds for reproducibility: tf.random.set_seed()
- Use tf.keras.backend.clear_session() to reset state
- Implement proper input validation and preprocessing
- Use TensorBoard for training visualization and debugging
- Configure GPU memory growth to avoid OOM errors
- Use tf.debugging assertions for runtime validation
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.
- yesterday First seen · 50 lines · 413 tokens per session scan A ff1961fb115b
tensorflow is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 413 tokens to every session, about $0.0021 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-09-03.
Other cursor rules, from other repositories
r-cursorrules-prompt-file-best-practices
Cursor rules for R development with best practices integration.
pytorch-scikit-learn-cursorrules-prompt-file
Cursor rules for PyTorch development with scikit-learn integration.
pandas-scikit-learn-guide-cursorrules-prompt-file
Cursor rules for Pandas development with scikit-learn guide integration.
data-science
Rules for data science, ML, and Jupyter notebook work.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
50-rag-system
Retrieval-augmented generation rules.