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 aiwg-steward-routing-referencegit 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/aiwg-steward-routing-reference)<a href="https://agentmods.dev/skills/jmagly/aiwg/aiwg-steward-routing-reference"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-steward-routing-reference/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/aiwg-steward-routing-reference"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-steward-routing-reference.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.00038 | $0.00463 |
| Opus 5 | $0.00019 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
aiwg-steward-routing-reference 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 9d 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.
What it actually says
AIWG Steward Routing Reference
Tier-3 reference for aiwg-steward. Use this only after the Tier-1 steward
definition or steward-quickref points here.
Read the full reference at:
agentic/code/addons/aiwg-utils/docs/agent-examples/aiwg-steward-routing-reference.md
Contains
- Tier-2 / Tier-3 loading protocol.
- Setup repair and cleanup routing:
status --probe,doctor,refresh,use,regenerate, index rebuild/sync, and provider reload boundaries. - Issue workflow routing:
issue-workflow-guide,issue-audit,address-issues, andaiwg-issueboundaries. - Project-local authoring routing:
aiwg new-bundle,aiwg new-extension,aiwg new-provider, and customization docs. - Kernel-pivot deploy model and provider deploy paths.
$AIWG_ROOTreadability diagnostic and per-project-copy fallback.- Full CLI toolset table.
- Command routing examples and invocation patterns.
- Catalog search by capability.
- Orchestration and loop routing, including
/goal,/aiwg-mission, cross-stack Mission,runtime:<name>,activity-log, andbest-output.
If this reference contradicts current CLI output, retry once with a broader discover phrase, run the steward repair ladder for stale discovery when appropriate, then file an AIWG correction issue with the stale target and observed command output.
References
- [[steward-quickref]]
- [[aiwg-steward worked examples]]
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/docs/agent-examples/aiwg-steward-routing-reference.md
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.
- 9d ago First seen · 46 lines · 38 tokens per session scan A fdc24cd27361
aiwg-steward-routing-reference is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 463 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-09-03.
Other skills, from other repositories
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-class-cycle
Run one DOS plan-class lifecycle tick from the workspace [lifecycle] table: evaluate declared transitions, have a judge approve/defer them, write gated plan-meta edits, and log the cycle. Use when gardening plan lifecycle classes automatically.
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
task-copilot
Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context.