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 skills add jmagly/aiwg --skill setup-validategit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/setup-validate)<a href="https://agentmods.dev/skills/jmagly/aiwg/setup-validate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/setup-validate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jmagly/aiwg/setup-validate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/setup-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 81 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium Agent Snooping · line 133 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 134 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.1 | $0.00023 | $0.01366 |
| Opus 5.5 | $0.00009 | $0.00546 |
| Sonnet 5.5 | $0.00005 | $0.00273 |
| Haiku 4.5 | $0.00002 | $0.00137 |
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 1mo 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 — 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
apiVersionmust besetup.aiwg.io/v1kindmust beSetupManifest- 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_typemust be one of:user,developer,ci(if present)metadata.execution_modemust bedeterministicorprovider-orchestrated(if present)
Reference Checks
- Every
script:path exists relative to the manifest directory - Every
chain:manifest path exists - Every
platform-routeroute value resolves to an existing script depends_onstep IDs all exist in the manifest- Recovery
triggerslist references valid step IDs os-configsteps:config_idmust reference a valid entry inspec.os_config
Developer Manifest Checks (when metadata.install_type: developer)
These checks apply only to manifests with install_type: developer:
Errors
os-configsteps must reference a validconfig_idin thespec.os_configblockinteractive_required: trueparams must not have adefaultvalue — a default defeats the purpose of requiring interactive input- Each platform declared in
spec.platformsmust have at least one platform-specific step oros_configentry
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.
- 1mo ago First seen · 135 lines · 23 tokens per session scan A 88f5a21de753
setup-validate is a skill published in the GitHub repository jmagly/aiwg (224 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.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
builder
Implementing robust business logic, API integrations, data models, and reproducible AI image-generation code with type safety. Use for production implementation, Gemini image API pipelines, or interactive pair programming.
matrix
Controlling combinatorial explosion across multi-dimensional axes: minimum coverage sets, execution plans, test/deploy/UX/risk prioritization. Use when scoping multi-axis combinations.
nexus
Orchestrating multi-specialist task chains and scope-adaptive product delivery: classifies intent, selects and executes the minimum viable chain, aggregates results, and verifies acceptance criteria. For multi-domain tasks, build-first delivery, and product lifecycle execution.
oracle
Designing and evaluating AI/ML systems: prompt engineering, RAG design, LLM application patterns, AI safety, evaluation frameworks, MLOps, cost optimization. Use for AI pipelines or eval harnesses.
scribe
Authoring standalone and cross-team specifications: PRD/SRS/HLD/LLD, staged L0-L4 unified packages, BDD acceptance criteria, and traceability. Use for technical or multi-audience documentation; not implementation or architecture decisions.
tome
Converting technical knowledge into durable learning documents and publishable articles. Use for diff-based teaching, decision records, onboarding, note/Zenn/Qiita/dev.to posts, article series, retrospectives, and cross-platform repurposing.