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/rossoctl/examples/skills-validatenpx skills add rossoctl/examples --skill skills-validategit clone --depth 1 https://github.com/rossoctl/examplesWhat 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.00014 | $0.01275 |
| Opus 5 | $0.00007 | $0.00638 |
| Sonnet 5 | $0.00003 | $0.00255 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
skills:validate 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Skill
When to Use
- After creating or editing a skill
- Before committing skill changes
- When auditing all skills for consistency
Validation Checks
Required
- Frontmatter: Has
name:anddescription:fields - Colon naming:
name:uses colon notation (e.g.,tdd:cinottdd-ci) - Directory match: Directory name matches frontmatter
name:field - Title: Has
# Skill Nameas first heading - When to Use: Has "When to Use" or "Overview" section
- Related Skills: Has "Related Skills" section at the end
- Mermaid diagram: Workflow/router skills have an embedded mermaid diagram
- Diagram colors: classDef colors match README color legend
Command Format (Required)
- Sandbox classification: Skill is classified as sandbox or management (see below)
- Single commands: Sandbox skills use one command per code block (no
&&chaining) - Auto-approve coverage: All commands in sandbox skills match a pattern in
.claude/settings.json - No multiline bash: Sandbox skills avoid heredocs, multiline pipes, or
forloops in commands
Recommended
- TOC: Table of Contents present if skill > 50 lines
- Placeholders: All commands are copy-pasteable (no unexplained placeholders)
- Task tracking: TDD/RCA skills have "Task Tracking" section
- Parent ref: Parent category
SKILL.mdreferences this skill - Imperative voice: Uses "Run X" not "You should run X"
- Length: Leaf skills are 80-200 lines (300 max)
- Diagram-text match: Diagram nodes correspond to textual flow steps
Sandbox vs Management Classification
Skills operate on either sandbox (safe) or management (requires approval) targets:
| Type | Target | Auto-approve? | Command format |
|---|---|---|---|
| Sandbox | Local Kind cluster, custom HyperShift hosted cluster | YES | Single commands, one per step |
| Management | Management cluster, AWS resources, git push, destructive ops | NO | Can chain commands (user approves anyway) |
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 · 150 lines · 14 tokens per session scan A 288489e01cf9
skills:validate is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,275 once invoked, about $0.0001 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
agent-challenges
Agent skill for challenges - invoke with $agent-challenges.
story-long-analyze
长篇网文拆文。深度拆解爆款长篇小说的黄金三章、人设架构、爽点设计、节奏控制。 单一深度拆解管道：跑完黄金三章（Stage 1）后产出快速预览报告并询问是否继续全量拆解， 确认后从 Stage 2 续跑逐章摘要、聚合分析、设定关系、汇总报告，全程产物落盘 拆文库/{书名}/。 触发方式：/story-long-analyze、/长篇拆文、「帮我拆这本书」「拆这本书」「分析黄金三章」 「深度拆解」「完整拆解」「系统拆解」或提供小说文本文件路径——全部进入同一管道。.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.