agentmods.dev

setup-validate

setup-validate is a skill for Claude Code, Codex from jmagly/aiwg. It costs 23 tokens per session (1,366 once invoked), scanned A, original, MIT.

A checker for setup.aiwg.io/v1 SetupManifest files. It compares the manifest with the required format and reports invalid fields, unsupported step types, and consistency problems.

In plain words
What is it for?
Use it to validate, strictly lint, or verify a setup.manifest.yaml file and its schema requirements.
Why use it?
It catches installation-manifest errors before the setup process runs; it reports issues rather than applying automatic fixes.

Skill for Claude CodeCodex

not rated 208 today A scan 23 tokens original MIT
View the source file jmagly/aiwg
Install

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.

agentmods
npx agentmods add skills/jmagly/aiwg/setup-validate
Any agent
npx skills add jmagly/aiwg --skill setup-validate
Clone the repo
git clone --depth 1 https://github.com/jmagly/aiwg

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for setup-validate

README.md
[![agentmods](https://agentmods.dev/badge/skills/jmagly/aiwg/setup-validate.svg)](https://agentmods.dev/skills/jmagly/aiwg/setup-validate)
Your own site
<a href="https://agentmods.dev/skills/jmagly/aiwg/setup-validate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/setup-validate.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,366 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.01366
Opus 5 $0.00012 $0.00683
Sonnet 5 $0.00005 $0.00273
Haiku 4.5 $0.00002 $0.00137

Measured 3d ago against content hash 88f5a21de753, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-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 3d 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.

agentic/code/addons/agentic-installer/skills/setup-validate/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

setup-validate

Validate a setup.aiwg.io/v1 SetupManifest file against the schema and run consistency checks.

Trigger Phrases

  • "validate setup manifest"
  • "check setup.manifest.yaml"
  • "aiwg setup-validate [manifest]"
  • "lint installer manifest"
  • "verify my setup manifest"

Parameters

manifest (positional, optional)

Path to the setup.manifest.yaml. Default: ./setup.manifest.yaml.

--schema (optional)

Path to schema file. Default: auto-located from AIWG installation.

--strict (optional)

Fail on warnings in addition to errors.

--fix (optional)

Reserved for future safe autofixes. The current CLI validates and reports only.

Validation Checks

Schema Validation

  • apiVersion must be setup.aiwg.io/v1
  • kind must be SetupManifest
  • Required fields present: metadata.name, spec.platforms, spec.steps
  • All step types are one of: script, detect, ask, verify, agentic, platform-route, chain, os-config
  • Param types are one of: string, path, boolean, integer, choice
  • metadata.install_type must be one of: user, developer, ci (if present)
  • metadata.execution_mode must be deterministic or provider-orchestrated (if present)

Reference Checks

  • Every script: path exists relative to the manifest directory
  • Every chain: manifest path exists
  • Every platform-route route value resolves to an existing script
  • depends_on step IDs all exist in the manifest
  • Recovery triggers list references valid step IDs
  • os-config steps: config_id must reference a valid entry in spec.os_config

Developer Manifest Checks (when metadata.install_type: developer)

These checks apply only to manifests with install_type: developer:

Errors
  • os-config steps must reference a valid config_id in the spec.os_config block
  • interactive_required: true params must not have a default value — a default defeats the purpose of requiring interactive input
  • Each platform declared in spec.platforms must have at least one platform-specific step or os_config entry

Read the full file on GitHub · 135 lines

Changes

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.

  1. 3d ago First seen · 135 lines · 23 tokens per session scan A 88f5a21de753

Subscribe to this mod's changes

setup-validate is a skill published in the GitHub repository jmagly/aiwg (208 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,366 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.

Autonomous Agentsagentic-codingai-frameworkanthropicclaude-codecodex
Related

Other skills, from other repositories

hunt

Compose a guided or automatic shift from the ready catalog, then review it first or run it directly under one time budget. Use when the owner wants to choose jobs or let Nightshift find the highest-value applicable work.

orwa-mahmoud/nightshift · 45 tokens

archive

File the finished part of the run state into a dated archive — shipped items, research, opportunities, the rotated journal, and handled snags. The live files stay lean; the facts stay on disk.

orwa-mahmoud/nightshift · 43 tokens

doctor

Read-only Nightshift diagnosis — workspace, rules, markers, session, process lease, watchman, deadline, and classified next actions. Use when a shift looks wrong, recovery is unclear, or the owner asks what Nightshift sees. Never repairs by being invoked.

orwa-mahmoud/nightshift · 55 tokens

import-issues

Stage explicitly selected GitHub issues onto the drafting table as quoted source. Never searches, never writes back to GitHub, never installs gh.

orwa-mahmoud/nightshift · 32 tokens

purge

Permanently delete this project's Nightshift state. Does not uninstall the plugin.

orwa-mahmoud/nightshift · 19 tokens

stop

Issue a stop-work order — pause the shift immediately, leaving unfinished items open.

orwa-mahmoud/nightshift · 18 tokens