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/opendcai/dataflow-webui/webui-change-policygit clone --depth 1 https://github.com/OpenDCAI/DataFlow-WebUIWhat 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.00000 | $0.00827 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
webui-change-policy 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebUI Change Policy (MANDATORY)
Allowed Changes
You may ONLY make the following types of changes to the WebUI frontend and backend:
1. Operator Rendering Support (Frontend)
Add or fix rendering for DataFlow operators that are not yet properly displayed in the WebUI pipeline canvas.
What this means:
- Add a new node component in
components/manage/mainFlow/nodes/for an operator type that renders as a broken/empty box - Fix parameter rendering in operator config panels (e.g.,
promptParamModel, init/run param editors) - Add missing operator-specific UI elements (e.g., a special param editor for a new param type)
- Fix display bugs for operators that exist in DataFlow but show incorrectly in the canvas
How to verify an operator is "not yet supported":
- It exists in the DataFlow
OPERATOR_REGISTRY(check viaGET /api/v1/operators/) - But the WebUI does not render it properly (broken node, missing params, crash on open)
2. Operator API Support (Backend)
Add or fix API endpoints that serve existing DataFlow operator/pipeline/serving/dataset data to the frontend.
What this means:
- Add a missing CRUD endpoint for an existing DataFlow resource type
- Fix serialization of operator parameters that the frontend cannot parse
- Fix edge cases in existing endpoints (e.g., null handling, pagination bugs)
- Add query params or filters to existing list endpoints
Prohibited Changes
You MUST NOT:
| Prohibited Action | Example |
|---|---|
| Create new analytical pages/dashboards | Taxonomy Analytics page, custom report pages |
| Create new backend endpoints for derived/computed data | /api/v1/taxonomy/analytics, /api/v1/custom-stats |
| Add new navigation items to the sidebar | New entries in navList in manage/index.vue |
Add new routes in router/Manage/index.js |
New { path: 'xxx', component: ... } entries |
Create new views/manage/*/index.vue pages |
Any new top-level manage page |
Add new services/registries in core/container.py |
New self.xxx_registry attributes |
Add new config paths in core/config.py |
New XXX_REGISTRY settings |
| Build feature-level functionality not tied to operator rendering | Anything beyond making existing operators work in the UI |
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 · 80 lines · 0 tokens per session scan A e58b04e8d8d0
webui-change-policy is a cursor rule published in the GitHub repository OpenDCAI/DataFlow-WebUI (224 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 827 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-30.
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.