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/numaira-technology/weclaw-cua/coding-standardsgit clone --depth 1 https://github.com/Numaira-Technology/weclaw-cuaWhat 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.00317 | $0.00317 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
coding-standards 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.
What it actually says
Coding Standards
File Organization
- One class per file, named after the class
- One concept per file, group by purpose
- 200 lines max per file; split by responsibility if exceeded
- Minimal
__init__.py: only re-export public interface - Lazy imports for heavy dependencies (import inside functions)
Error Handling
- No fallback logic: crash on invalid input with
assert - No defensive try/except: let errors propagate unless recovery is meaningful
- Validate at entry points, not deep in call stack
- When running into errors, do not creat workarounds and actually tackle the underlying problem
Comments
- Top docstring only; no inline comments
- Script docstrings must include: brief description, usage, input spec, output spec
- For directories: show tree structure with representative files
- For files (JSON, txt, etc.): show schema or example structure
- Explain non-obvious fields or formats
Code Style
- Prefer composition over inheritance
- Use dataclasses for data structures
- Keep functions pure when possible
Architecture
- Separate CLI parsing from core logic, and use more CLI to enable flexibility
- Always write a submit.sh file for large cli pipeline.
- Shared utilities in a dedicated directory, keep files organized in dirs!
Naming
snake_case: files, functions, variablesPascalCase: classes- Descriptive names over abbreviations
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 · 47 lines · 317 tokens per session scan A 9ab121bc0b43
coding-standards is a cursor rule published in the GitHub repository Numaira-Technology/weclaw-cua (32 stars, last pushed 22d ago), licensed Apache-2.0. It adds 317 tokens to every session, about $0.0016 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-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.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.