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 stewardgit 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/steward)<a href="https://agentmods.dev/skills/jmagly/aiwg/steward"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/steward/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/steward"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/steward.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.04916 |
| Opus 5.5 | $0.00009 | $0.01966 |
| Sonnet 5.5 | $0.00005 | $0.00983 |
| Haiku 4.5 | $0.00002 | $0.00492 |
Grade A, and why
steward 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 6d 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
steward
You provide provider capability awareness and intelligent command routing. You read the canonical capability matrix to answer what the current provider supports natively, what must be emulated, and which command achieves a given goal on the active platform.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "what can this provider do" → capabilities for current provider
- "is X supported here" → feature check for current provider
- "how do I do X" (in provider context) → routing advice
- "what command handles Y" → find subcommand
- "which model should this use" → model policy route
- "model catalog or routing" →
aiwg steward models - "install or repair AIWG" → public provider-orchestrated setup manifest
- "AIWG setup is stale/broken" → steward repair ladder
- "refresh provider files" → status/doctor, dry-run refresh, then provider redeploy
- "clean up AIWG issues" → discover
issue-audit,aiwg-issue, oraddress-issues
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Current provider capabilities | "what does my provider support" | aiwg steward capabilities |
| Named provider capabilities | "what does Cursor support" | aiwg steward capabilities --provider cursor |
| All providers | "show the full capability matrix" | aiwg steward capabilities --all |
| Feature check | "does my provider support agent teams" | aiwg steward capabilities --feature agent_teams |
| Routing lookup | "which providers support cron" | aiwg steward find --capability cron |
| Model routing | "which model should this use" | aiwg steward models; then aiwg models audit or aiwg models resolve |
| Install or repair AIWG | "get AIWG working in this project" | Follow the public setup.aiwg.yaml; use the self-verifying deployment result, with status and doctor only for audit or recovery |
| Stale provider files | "Codex says skills are missing" | aiwg status --probe --json, aiwg doctor, aiwg refresh --dry-run, then aiwg use all --provider <provider> or aiwg refresh --provider <provider> |
| Stale bootstrap/context | "doctor says the precedence is superseded", "WORKSPACE.md looks wrong", precedence-superseded / precedence-missing / authority-missing |
aiwg workspace-context doctor, then aiwg regenerate to rewrite the managed blocks; re-run the doctor to confirm healthy |
| Rules not being honored | "the agent ignored an AIWG rule and cited harness instructions" | Check aiwg doctor → "Workspace context graph". A missing or superseded precedence means the bootstrap never asserted rule authority; aiwg regenerate restores it |
| Stale discovery | "discover cannot find a known skill" | Rebuild and sync the framework index, then re-run discovery |
| Issue cleanup | "clean up stale issues" | Discover first: issue-audit for backlog cleanup, address-issues for implementation, aiwg-issue for AIWG product issues |
| Jev decision offload | "help me set up jev", "use my jev token" | Follow the Jev setup routing below, then the decision-offload rule |
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.
- 6d ago Changed · +2 lines 9d7ef6400978
- 10d ago Changed ffb60ed6385c
- 20d ago Changed · +60 lines 627d01d13fc1
- 27d ago Changed · +39 lines 0bda21c3018c
- 1mo ago Changed · +7 lines e34e7463ed66
- 1mo ago Changed · +9 lines a41451719b3c
- 1mo ago Changed · +2 lines 1dabdde9b14d
- 1mo ago First seen · 336 lines · 23 tokens per session scan A 94b956187def
steward is a skill published in the GitHub repository jmagly/aiwg (227 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 4,916 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-09-05.
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.
cue
Writing and producing product videos: scripts, storyboards, narration, and reproducible Playwright demo recordings. Use for explainers, onboarding, feature walkthroughs, multi-aspect exports, captions, and video quality checks.
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.
palette
Improving usability, interaction quality, cognitive load reduction, feedback design, and a11y compliance. Use when improving UX usability or interaction feel.
pixel
Generating pixel-accurate HTML/CSS code from image mockups (PNG/JPG/screenshots) and performing visual verification for faithful reproduction. Use when mockup-to-code generation is needed.