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/uipath/skills/content-qualitygit clone --depth 1 https://github.com/UiPath/skillsWhat 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.00311 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
content-quality 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
Primary audience is AI coding agents, not humans. Be prescriptive ("Run X") not descriptive ("You could run X"). Include exact CLI commands with all required flags. Use --output json on any command whose output the agent parses. Specify what to do when a command fails, not just the happy path. Number rules — agents follow numbered lists more reliably than prose. Include anti-patterns — "what NOT to do" prevents the most expensive mistakes.
Markdown: ATX headers (#, ##), no underline-style. Fenced code blocks with language identifiers (```bash, ```yaml, ```csharp, ```json). Tables for structured data. > blockquotes for warnings. Heading hierarchy must not skip levels.
CLI docs: use <PLACEHOLDER> (angle brackets, UPPER_SNAKE_CASE) for user-provided values. Specify required vs optional flags. Shell commands must use Unix syntax (never del/dir/nul); escape backslashes in Windows paths (C:\\path\\file.txt).
Do NOT include: marketing language, version-specific facts that will go stale (link to latest docs instead), duplicate content across files, auto-generated --help output, images or binary files.
Full reference: .claude/rules/content-quality.md.
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 · 15 lines · 0 tokens per session scan A e4073e9bb486
content-quality is a cursor rule published in the GitHub repository UiPath/skills (150 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 311 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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.