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/UiPath/skillsWrote 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/uipath/skills/skill-structure)<a href="https://agentmods.dev/rules/uipath/skills/skill-structure"><img src="https://agentmods.dev/badge/rules/uipath/skills/skill-structure/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/uipath/skills/skill-structure"><img src="https://agentmods.dev/badge/rules/uipath/skills/skill-structure.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.00000 | $0.00434 |
| Opus 5.5 | $0.00000 | $0.00174 |
| Sonnet 5.5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
skill-structure 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 1mo 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
Every skill under skills/uipath-<kebab-case>/ must have a SKILL.md with valid YAML frontmatter: name (matching folder name exactly) and description (under 1024 characters — repo cap; Claude Code's hard truncation for description + when_to_use is 1,536 chars).
The description must front-load skill identity and unique file/domain signals (e.g. .cs, .xaml, .flow, servo) within the first ~100 characters. Use compact → redirects for commonly confused sibling skills (e.g. For XAML→uipath-rpa). Start with [PREVIEW] for unstable skills. Do NOT use verbose TRIGGER when: / DO NOT TRIGGER when: clauses or nest fields under metadata: — both cause Claude Code to drop the field.
SKILL.md body order: Title → When to Use → Critical Rules (numbered) → Workflow/Quick Start → Reference Navigation → Anti-patterns. Reference files use kebab-case; guides end with -guide.md; templates end with -template.md or -template.<ext>. Skills must be self-contained — no cross-skill references.
Full reference: .claude/rules/skill-structure.md.
Before changing flavor markers, sparse overrides, generic discovery,
package construction, publishing, or flavor CI, read
.claude/skills/manage-skill-flavors/SKILL.md completely and follow its
reference-routing instructions.
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.
- 1mo ago First seen · 18 lines · 0 tokens per session scan A 25dfc3f9156f
skill-structure is a cursor rule published in the GitHub repository UiPath/skills (171 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 434 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
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).