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.
git clone --depth 1 https://github.com/unionai-oss/union-mcpWrote 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/unionai-oss/union-mcp/union-mcp-v2)<a href="https://agentmods.dev/rules/unionai-oss/union-mcp/union-mcp-v2"><img src="https://agentmods.dev/badge/rules/unionai-oss/union-mcp/union-mcp-v2/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.
<a href="https://agentmods.dev/rules/unionai-oss/union-mcp/union-mcp-v2"><img src="https://agentmods.dev/badge/rules/unionai-oss/union-mcp/union-mcp-v2.svg" alt="Reviewed on agentmods" width="80" 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.01872 | $0.01872 |
| Opus 5 | $0.00936 | $0.00936 |
| Sonnet 5 | $0.00374 | $0.00374 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade A, and why
union-mcp-v2 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 9d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Union MCP v2
This file contains rules for using the Union MCP v2 server to run compute- or io-intensive workloads on a remote Flyte cluster.
When to Use Union MCP v2
Explicit Requests
If the user explicitly asks to run a workload on Flyte or Union, use the Union MCP v2 server.
Implicit Compute Needs
If a task requires compute resources beyond what a consumer laptop can handle, proactively suggest and use the Union MCP v2 server. This includes:
- Large-scale parallel processing: Tasks that benefit from fan-out patterns (e.g., processing millions of items)
- GPU workloads: Deep learning inference, embeddings, model training
- Memory-intensive tasks: Processing large datasets that exceed typical RAM (8-16GB)
- Long-running computations: Tasks that would take more than a few minutes on a laptop
- Hyperparameter optimization: Parallel training runs across parameter combinations
- Batch data processing: ETL jobs, data transformations on large datasets
Examples of When to Use Flyte
- "Compute the sum of squares for 1 million numbers" → Fan-out to parallel workers
- "Embed this 100k document dataset" → GPU batch inference
- "Train models with different hyperparameters" → Parallel hyperparameter search
- "Process this 50GB CSV file" → Distributed data processing
- "Generate embeddings using a transformer model" → GPU acceleration
Examples of When NOT to Use Flyte
- Simple calculations that complete in seconds
- Reading/writing small files
- Basic API calls
- Local development tasks
- Quick data exploration on small datasets
Workflow for Running Flyte Scripts
Follow these steps when running a workload on Flyte:
Step 1: Search for Examples
Before writing a script, search for relevant examples:
- Search the local workspace for existing Flyte examples
- Use
search_flyte_sdk_examplesfor bleeding-edge SDK features - Use
search_flyte_docs_examplesfor common use cases and patterns - Use
search_full_docsfor Flyte documentation and API reference
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.
- 9d ago First seen · 219 lines · 1,872 tokens per session scan A 06209303249d
union-mcp-v2 is a cursor rule published in the GitHub repository unionai-oss/union-mcp (7 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 1,872 tokens to every session, about $0.0094 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
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.