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 skills add UiPath/skills --skill uipath-aopsgit 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/skills/uipath/skills/uipath-aops)<a href="https://agentmods.dev/skills/uipath/skills/uipath-aops"><img src="https://agentmods.dev/badge/skills/uipath/skills/uipath-aops/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/skills/uipath/skills/uipath-aops"><img src="https://agentmods.dev/badge/skills/uipath/skills/uipath-aops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 3 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00174 | $0.06271 |
| Opus 5 | $0.00087 | $0.03136 |
| Sonnet 5 | $0.00035 | $0.01254 |
| Haiku 4.5 | $0.00017 | $0.00627 |
Grade A, and why
uipath-aops scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
13. **Re-implementing in raw REST.** `uip aops` handles the StudioAdmin base paths (`/{orgId}/roboticsops_/sourcecontrol_/`, `/{orgId}/roboticsops_/cicd_/`), pagination, and the `Result/Code/Data` envelope. Never `curl` How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UiPath StudioAdmin AOps — Source Control + CICD Pipelines
Depends on the @uipath/aops-tool CLI plugin; install via uip tools install @uipath/aops-tool before using.
Tool migration.
@uipath/sc-tool(uip sc) and@uipath/cicd-tool(uip cicd) were unified into@uipath/aops-tool(uip aops).@uipath/cicd-toolis gone from npm. Everyuip sc <verb>anduip cicd <verb>becomesuip aops <verb>— the verb trees merged without renaming any subcommand. See migration-guide.md.
Build a StudioAdmin CICD pipeline that binds two independent things:
- Source — one Studio project the pipeline checks out on every run. Two equivalent ways to reach it:
- Solution path — a project inside a Studio Solution surfaced by
aops connection solutions <connection-id> - Standalone-project path — a project surfaced directly by
aops connection projects <connection-id>(no enclosing Solution)
- Solution path — a project inside a Studio Solution surfaced by
- Target — an already-published Orchestrator automation process surfaced by
aops pipeline processes. The pipeline runs / updates this process as part of its execution.
When to Use This Skill
- User wants a new pipeline for a Studio Solution or standalone project already synced to StudioAdmin
- User names a published Orchestrator process and wants a pipeline that runs / updates it
- User says "create / build / wire a pipeline" against a Solution or a process
- User wants a one-shot "create and run" with execution id + log follow
- User wants to inspect or kick off an existing pipeline run, or edit one after creation
- User wants to inspect SourceControl state — connections, repos, branches, project files, commit history
Do NOT use this skill for:
- AOps governance policies (
uip gov aops-policy— Studio / Robot feature restrictions) →uipath-governance. Same "AOps" word, different product surface. - Packing or publishing a
.nupkg(uip solution pack/publish/deploy) →uipath-platform - Authoring or editing workflow code (
.xaml,.cs) →uipath-rpa - Creating the SourceControl connection itself — connections are UI-only via the StudioAdmin web app
- Publishing a new process — processes are published separately (Studio publish /
uip solution publish)
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 314 lines · 174 tokens per session scan A 72d0cc62751e
uipath-aops is a skill published in the GitHub repository UiPath/skills (155 stars, last pushed yesterday), licensed MIT. It adds 174 tokens to every session and 6,271 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.