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 skills/abilityai/abilities/validate-pipelinenpx skills add Abilityai/abilities --skill validate-pipelinegit clone --depth 1 https://github.com/Abilityai/abilitiesWhat 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.00055 | $0.02179 |
| Opus 5 | $0.00028 | $0.01090 |
| Sonnet 5 | $0.00011 | $0.00436 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
validate-pipeline 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Pipeline
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.validate-pipeline vX.Y — recent: <summary>. Then proceed.
Read-only linter. Verify a pipeline.yaml is structurally sound. Surfaces errors and warnings; writes no files.
Run this:
- After any manual edit to
pipeline.yaml - Automatically at the end of
/add-pipelineand/add-pipeline-stage - Before deploying the agent to a new environment
The heartbeat (pipeline-tick) reads pipeline.yaml directly each tick. It does not require this skill to have run. If you ship a broken pipeline.yaml, the heartbeat will fail loudly on the next tick — running the linter just gets you that feedback sooner.
Process
Step 1: Resolve target
Expect <pipeline-slug> as the single positional argument. If missing, list pipelines and prompt.
Validate projects/<slug>/pipeline.yaml exists.
Step 2: Schema check
Required top-level keys: schema_version, pipeline_id, name, stages, heartbeat.
PIPELINE_FILE="projects/$SLUG/pipeline.yaml"
SCHEMA=$(yq '.schema_version // 0' "$PIPELINE_FILE")
[ "$SCHEMA" = "1" ] || error "schema_version must be 1 (got: $SCHEMA)"
ID=$(yq '.pipeline_id // ""' "$PIPELINE_FILE")
[ "$ID" = "$SLUG" ] || error "pipeline_id ($ID) doesn't match directory slug ($SLUG)"
STAGE_COUNT=$(yq '.stages | length' "$PIPELINE_FILE")
[ "$STAGE_COUNT" -gt 0 ] || error "No stages defined"
yq '.heartbeat.cron' "$PIPELINE_FILE" >/dev/null || error "heartbeat.cron is required"
yq '.heartbeat.message' "$PIPELINE_FILE" >/dev/null || error "heartbeat.message is required"
yq '.heartbeat.name' "$PIPELINE_FILE" >/dev/null || error "heartbeat.name is required"
Collect all errors and report at the end — don't stop on the first one.
Step 3: Stage-level checks
For each stage in .stages[]:
yq '.stages[] | [.id, .skill, .timeout_seconds, (.retry.max_attempts // 1), (.on_failure // "escalate")] | @tsv' "$PIPELINE_FILE"
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 · 190 lines · 55 tokens per session scan A 6850a8633b3a
validate-pipeline is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 55 tokens to every session and 2,179 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.