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 runtime-infogit 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/runtime-info)<a href="https://agentmods.dev/skills/jmagly/aiwg/runtime-info"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/runtime-info/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/runtime-info"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/runtime-info.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.01137 |
| Opus 5.5 | $0.00009 | $0.00455 |
| Sonnet 5.5 | $0.00005 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
runtime-info 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Info
You display a comprehensive runtime environment report — detected provider, available tools and permissions, AIWG version, installed frameworks, and relevant environment variables. Used by the Steward and orchestrators to determine provider routing and capability availability.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "what provider am I on" → runtime-info (provider section)
- "do I have bash access" → runtime-info (tools section)
- "what version of aiwg is this" → runtime-info (version section)
- "what's installed" → runtime-info (frameworks section)
- "check my environment" → runtime-info
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Full report | "show runtime info" | Run aiwg runtime-info |
| Provider check | "which provider is active?" | Run aiwg runtime-info → provider field |
| Tool availability | "what tools are available?" | Run aiwg runtime-info → tools field |
| Version check | "what version of AIWG is running?" | Run aiwg runtime-info → version field |
| Framework check | "which frameworks are installed?" | Run aiwg runtime-info → frameworks field |
| Environment dump | "show environment variables" | Run aiwg runtime-info → env field |
Behavior
When triggered:
-
Identify what the user wants:
- Full report, or a specific field (provider, tools, version, frameworks, env)?
- Is this for routing decisions (Steward context) or user curiosity?
-
Run the command:
# Full runtime report aiwg runtime-info # Machine-readable (for orchestration / Steward routing) aiwg runtime-info --json -
Extract and present the relevant section if the user asked about a specific aspect; present the full report otherwise.
Report Fields
The runtime-info report covers:
| Field | Description |
|---|---|
provider |
Detected AI platform (claude-code, copilot, cursor, etc.) |
aiwg_version |
Installed AIWG version (CalVer) |
node_version |
Node.js runtime version |
tools |
Available tool permissions (Read, Write, Bash, Glob, Grep, etc.) |
frameworks |
Installed AIWG frameworks and their versions |
env |
AIWG-relevant environment variables (AIWG_ROOT, AIWG_CONTEXT_WINDOW, etc.) |
platform |
OS and architecture |
cwd |
Current working directory |
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 · 151 lines · 23 tokens per session scan A c80d4c1155d0
runtime-info 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,137 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.