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 sessiongit 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/session)<a href="https://agentmods.dev/skills/jmagly/aiwg/session"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/session/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/session"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/session.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.00024 | $0.00942 |
| Opus 5.5 | $0.00010 | $0.00377 |
| Sonnet 5.5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
session 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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWG Session
Start a fully-prepared agentic session. Pre-flight checks run automatically: version currency, health diagnostics, and deployment verification. Issues are auto-repaired before launch. Pass mcp to inject configured MCP servers into the provider config first.
For past conversations, cross-provider timelines, or catalog queries, use
aiwg show skill session-explore --body. The plural aiwg sessions namespace manages
history; this skill launches a new provider session.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "start a session" →
aiwg session - "launch claude" →
aiwg session --provider claude - "start with mcp" →
aiwg session mcp - "start fresh" →
aiwg session(triggers full pre-flight) - "launch codex" →
aiwg session --provider codex
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Default launch | "start a session" | aiwg session |
| Explicit provider | "launch with codex" | aiwg session --provider codex |
| With MCP | "start with my MCP servers" | aiwg session mcp |
| MCP + provider | "launch cursor with MCPs" | aiwg session mcp --provider cursor |
| Skip repair | "just launch, skip checks" | aiwg session --no-repair |
Behavior
When triggered:
-
Resolve provider:
--providerflag → project configproviders[0]→ user config →claude -
Pre-flight (auto-repair enabled by default):
- Version check — updates aiwg if stale
- Health check (
aiwg doctor) — auto-repairs fixable issues - Deployment check — redeploys missing framework files
- If repair fails: offers full reinstall + redeploy
- If unresolvable: surfaces
aiwg feedback --type bug
-
MCP inject (when
mcpsubcommand is used):aiwg mcp inject --provider <provider> -
Launch:
- Spawnable providers (claude, codex, opencode): launches the binary directly
- IDE providers (cursor, windsurf, copilot, factory, warp): prints ready instructions
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.
- 4d ago Changed 4b1fc6f707fe
- 1mo ago Changed · +3 lines d7a482179ea6
- 1mo ago First seen · 119 lines · 24 tokens per session scan A 1397dd3021bb
session is a skill published in the GitHub repository jmagly/aiwg (224 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 942 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
rally
Orchestrating multi-session parallel execution via Claude Code Agent Teams API and Codex CLI Subagents — launch, manage, coordinate concurrent tasks. Use when parallel work is needed.
void
Verifying YAGNI, cutting scope, and proposing complexity reductions. A 'subtraction' agent questioning the justification for every feature, dependency, doc, and config. Does not write code.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development methodology with multi-agent orchestration. Use when running a structured spec-to-code workflow or decomposing a feature through the SPARC phases.
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows. Use when piping output between agents/tools as streaming JSON or building a sequential transform pipeline.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
session-handoff-packager
Packages session work into a local handoff document for continuity. Use for: session summary, handoff, save what we did, continue next time.