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/lint-taskgit 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/lint-task)<a href="https://agentmods.dev/commands/uipath/skills/lint-task"><img src="https://agentmods.dev/badge/commands/uipath/skills/lint-task.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.04130 |
| Opus 5 | $0.00000 | $0.02065 |
| Sonnet 5 | $0.00000 | $0.00826 |
| Haiku 4.5 | $0.00000 | $0.00413 |
Grade A, and why
lint-task 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint coder-eval Task YAML
Review a coder-eval task YAML against a quality rubric and surface anti-patterns. Advisory only — does not modify files.
Input: $ARGUMENTS
- A path to one task YAML, e.g.
tests/tasks/uipath-maestro-flow/smoke/init_validate.yaml - Or a glob, e.g.
tests/tasks/uipath-platform/data-fabric/*.yaml - Or a directory, e.g.
tests/tasks/uipath-rpa/(lints every YAML beneath it)
Output: One markdown report per task, printed to chat. No file writes.
This command is the source of truth for the rubric. The PR-bot workflow (.github/workflows/lint-tasks.yml) reads this file and applies the same rubric to changed YAMLs at PR time.
Severity Levels
Every issue is tagged with one of four severities:
| Level | Meaning |
|---|---|
| Critical | Test cannot meaningfully validate the skill — must fix |
| High | Test is broken or misleading in a way that wastes infra cost or hides regressions — should fix before merge |
| Medium | Quality gap that reduces signal but doesn't break the test — should fix |
| Low | Polish — nice to have |
The task's overall verdict is the max severity across all issues raised. A task with no issues is OK.
Phase 1 — Resolve Targets
- Parse
$ARGUMENTS. - If it's a directory, glob
<dir>/**/*.yaml. - If it's a glob, expand it.
- If it's a single path, use it directly.
- Skip files under
_shared/— those are helper scripts, not task definitions. - If zero files match, print an error and stop.
For each resolved task file, run Phases 2–4 in parallel where possible.
Phase 2 — Read Task and Neighbors
For each target task file:
- Read the full YAML.
- List sibling task YAMLs in the same folder. These are the "nearby files" used for duplicate detection.
- Read up to 5 nearby files. If more exist, pick the 5 closest by shared tags (most tag-overlap first, ties broken by alphabetical filename).
- If the task is in a folder that only contains itself, expand the search to the parent skill directory and pick the same 5 by tag overlap.
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 · 265 lines · 0 tokens per session scan A 2705148cb71b
lint-task 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 4,130 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.