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/ruah-dev/ruah-orch/post-start-validationnpx skills add ruah-dev/ruah-orch --skill post-start-validationgit clone --depth 1 https://github.com/ruah-dev/ruah-orchWrote 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/ruah-dev/ruah-orch/post-start-validation)<a href="https://agentmods.dev/skills/ruah-dev/ruah-orch/post-start-validation"><img src="https://agentmods.dev/badge/skills/ruah-dev/ruah-orch/post-start-validation.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.00030 | $0.02456 |
| Opus 5 | $0.00015 | $0.01228 |
| Sonnet 5 | $0.00006 | $0.00491 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
post-start-validation 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 5d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/post-start-validation
Run after completing any task. Discovers what changed, applies governance gates, captures knowledge, commits and verifies.
0. Shell Rule
Detect OS. Use Git Bash syntax on Windows (forward slashes, /dev/null).
1. Determine Scope
git diff --name-only HEAD 2>/dev/null || git status --short
Classify changes by detecting file patterns:
- Frontend? —
.ts,.tsx,.js,.jsx,.css,.vue,.sveltefiles - Backend? —
.java,.kt,.py,.go,.rs,.rbfiles - Infrastructure? —
Dockerfile,docker-compose*,k8s/,.github/workflows/,*.tf - Docs-only? —
.mdfiles only outside source directories
Skip rules: Docs-only → skip code checks. Infra-only → skip local checks.
2. Read Governance Gates
Read .claude/governance.md
The governance file defines which gates to run and in what order. If it specifies "biome → tsc → build" — run exactly that. If it specifies "pytest" — run that. The gates are project-specific; this skill is not.
3. Run Gates
3.0. Workspace-aware gate execution
If the discovery cache indicates a workspace:
- Read root governance gates (from workspace root
.claude/governance.md) - Identify which members have changes: check
git diff --name-only HEADpaths - For changed members with their own governance: read member governance, merge with root gates
- Execute merged gates in order: root cross-stack gates first, then member-specific gates
Gate annotations (v2 format)
Path-scoped sections: ### Frontend (path: frontend/)
Before running any command in this section, cd into the specified directory. After the section completes, cd back to the project root. Example:
(cd frontend/ && npx biome check .) || exit 1
Conditional sections: ### TypeScript (if: tsconfig.json)
Skip the ENTIRE section if the referenced file does not exist at project root. Check before running any gate in the section:
[ -e tsconfig.json ] || echo "Skipping TypeScript gates (no tsconfig.json)"
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.
- 5d ago First seen · 298 lines · 30 tokens per session scan A f01b1914e489
post-start-validation is a skill published in the GitHub repository ruah-dev/ruah-orch (11 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 2,456 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…