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 commands/uipath/skills/skill-comparegit 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/commands/uipath/skills/skill-compare)<a href="https://agentmods.dev/commands/uipath/skills/skill-compare"><img src="https://agentmods.dev/badge/commands/uipath/skills/skill-compare.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.05550 |
| Opus 5 | $0.00000 | $0.02775 |
| Sonnet 5 | $0.00000 | $0.01110 |
| Haiku 4.5 | $0.00000 | $0.00555 |
Grade A, and why
skill-compare 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 4d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Comparison Experiment
Run an apples-to-apples A/B comparison between two refs of the skills repo — each ref is either a branch or a commit SHA — and produce a decision-ready report. Automates the workflow described in tests/experiments/skill-comparison-playbook.md.
Input: $ARGUMENTS
<ref_a> <ref_b>— required, the two refs to compare. Each ref is either a branch name (local or remote-tracking) or a commit SHA (short or full, must already be in the local object database). The two refs can be any mix of the two kinds.<task_selector>— optional third argument. Restricts which tasks run. Defaults to all tasks (warn the user: this can be slow and expensive). Accepts three forms; pick the most specific one that fits the question:- Skill name (bare word):
uipath-maestro-flow→ all task files undertests/tasks/uipath-maestro-flow/. Use this when the comparison is scoped to one skill. - Tag filter with
tags:prefix:tags:smokeortags:smoke,init→ comma-separated tags, OR semantics (any task carrying any of these tags). Forwarded tocoder-eval run --tags. Use this for cross-skill slices like "only smoke tests" or "only e2e + connector tests". - Path glob with
paths:prefix:paths:tasks/uipath-maestro-flow/smoke/init_validate.yamlorpaths:tasks/*/smoke_*.yaml(comma-separated globs allowed). Use this when you want a hand-picked subset.
- Skill name (bare word):
<n_reps>— optional fourth argument. Reps per variant. Defaults to3. Accept integers 1–5.
Examples:
/skill-compare main feat/my-change uipath-maestro-flow— two branches, scoped to one skill./skill-compare main a1b2c3d uipath-maestro-flow— branch vs. commit SHA, scoped to one skill./skill-compare a1b2c3d e4f5g6h uipath-maestro-flow— two SHAs (compare two historical points)./skill-compare main feat/my-change tags:smoke— two branches, only smoke tests across all skills./skill-compare main feat/my-change tags:smoke,init 5— smoke OR init tasks, N=5./skill-compare main feat/my-change paths:tasks/uipath-maestro-flow/smoke/init_validate.yaml,tasks/uipath-maestro-flow/smoke/registry_discovery.yaml— two specific files./skill-compare main feat/my-change— all tasks across all skills, N=3 (slow + expensive; expect to be re-prompted at Phase 5).
Ref slugs (used in filenames and worktree paths):
- Branch: replace
/with-and strip any leadingorigin/. Example:feat/my-change→feat-my-change. - SHA: resolve to the 7-char short form via
git rev-parse --short. Example:a1b2c3defabc→a1b2c3d. Short SHAs are already filename-safe; no further transformation.
Output:
- A new experiment YAML at
tests/experiments/compare-<ref_a_slug>-vs-<ref_b_slug>.yaml - Worktrees at
../skills-<ref_a_slug>and../skills-<ref_b_slug>relative to the repo root - Run results under
tests/runs/compare-<ref_a_slug>-vs-<ref_b_slug>-<timestamp>/ - Comparison report at
tests/runs/compare-<ref_a_slug>-vs-<ref_b_slug>-<timestamp>/comparison-report.md
Working directory. Every phase runs from tests/. All git operations use git -C .. to target the repo root. Worktree paths like ../skills-<slug> resolve alongside the repo, one level above tests/.
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.
- 4d ago First seen · 322 lines · 0 tokens per session scan A d59916f0cad8
skill-compare is a command published in the GitHub repository UiPath/skills (154 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,550 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.