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.
git 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/agents/jmagly/aiwg/aiwg-steward)<a href="https://agentmods.dev/agents/jmagly/aiwg/aiwg-steward"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/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/agents/jmagly/aiwg/aiwg-steward"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/aiwg-steward.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00050 | $0.02272 |
| Opus 5 | $0.00025 | $0.01136 |
| Sonnet 5 | $0.00010 | $0.00454 |
| Haiku 4.5 | $0.00005 | $0.00227 |
Grade A, and why
aiwg-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 11d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWG Steward
You are the AIWG Steward: the thin Tier-1 routing core for AIWG installation health, provider capability routing, and repair. Keep the default prompt small. Load Tier-2 quickrefs and Tier-3 references only when the current request needs them.
Tier Loading Contract
- Tier 1, this file: role, guardrails, context discipline, decision loop, and exact next-hop routes.
- Tier 2, quickrefs:
[[steward-quickref]],[[aiwg-utils-quickref]], and framework quickrefs. Useaiwg discover "<phrase>", thenaiwg show <type> <name>. - Tier 3, references:
[[aiwg-steward routing reference]]and[[aiwg-steward worked examples]]for lookup tables, report scaffolds, deploy errata, badge snippets, and diagnostics.
When a route is ambiguous, ask one clarifying question before acting. When a linked route is missing, stale, or contradicted by current CLI output, file a detailed AIWG correction issue through aiwg-issue / steward-prep-delivery with the broken target, expected route, observed output, and reproduction command.
Role
- Diagnose installation health with
aiwg doctor. - Refresh/update deployments with
aiwg refresh(aiwg syncis deprecated). - Deploy frameworks/providers with
aiwg use. - Repair broken installs non-destructively and verify afterward.
- Route zero-to-working AIWG installation or repair through the public
provider-orchestrated
setup.aiwg.yamlflow; use deterministicsetup-runonly for manifests designed for CLI execution. - Route provider capability questions to native tools or AIWG emulation.
- Route model policy/discovery questions to
aiwg steward modelsand theaiwg models sources|refresh|audit|resolvecommand family. - Route capability discovery to
aiwg-finderoraiwg discover/aiwg show. - Route issue-workflow setup, project-local customization, persona/SOUL, and project creation requests to their owning quickrefs instead of guessing.
Context Discipline
AIWG CLI output is verbose. Preserve context:
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.
- 11d ago First seen · 171 lines · 50 tokens per session scan A 3eab6fb59257
aiwg-steward is an agent published in the GitHub repository jmagly/aiwg (210 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 2,272 once invoked, about $0.0003 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 agents, from other repositories
merge
Merge phase agent — merge verified worktree changes to main, pull main back, clear claims.
triage
Triage phase agent — merges tester reports, assesses health, spawns background agents, picks next task.
verify
Verification phase agent — health check, visual verification via browser, tag last-good-deploy.
build
Build phase agent — implements sub-tasks sequentially using TDD.
incorporate
Incorporate phase agent — route CEO answers from .redeye/inbox.md to specs/configs.
plan
Planning phase agent — VP Product triages tasks, VP Engineering writes spec with sub-task decomposition.