Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jmagly/aiwgnpx agentmods add skills/jmagly/aiwg/runWrote 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/run)<a href="https://agentmods.dev/skills/jmagly/aiwg/run"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/run/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/run"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 147 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00020 | $0.01039 |
| Opus 5.5 | $0.00008 | $0.00416 |
| Sonnet 5.5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
run 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run
You execute a named script defined in .aiwg/aiwg.config, or list all available scripts when no name is given.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "what scripts are available" → list scripts
- "run the deploy script" → run
deploy - "execute test script" → run
test - "aiwg run" → list if no name; run if name given
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Named run | "run the test script" | Run aiwg run test |
| Explicit list | "list aiwg scripts" | Run aiwg run (no args) |
| With args | "run deploy with flag --prod" | Run aiwg run deploy --prod |
| Unknown name | "run the build script" | Run aiwg run build; report if not found |
Behavior
When triggered:
-
Verify config exists:
- Read
.aiwg/aiwg.configto confirmscriptsblock is present. - If no config found, suggest
aiwg initto create one.
- Read
-
Extract arguments:
- Is a script name specified? If yes, run it.
- If no name, list all registered scripts with their shell commands.
- Are additional arguments passed through? Append them to the shell invocation.
-
Run the appropriate command:
# List all available scripts aiwg run # Run a named script aiwg run <script-name> # Run with pass-through arguments aiwg run <script-name> -- <extra-args> -
What "run" does:
- Reads the script's shell command from
.aiwg/aiwg.config - Executes it in the project root
- Streams output to the terminal
- Reports exit code on completion
- Reads the script's shell command from
-
Report the result — show the command that was executed, stream output, and confirm success or failure with exit code.
Examples
Example 1: List available scripts
User: "What scripts do I have registered in aiwg?"
Extraction: List request, no script name
Action:
aiwg run
Response:
Registered scripts (from .aiwg/aiwg.config):
test → npm test
lint → npm run lint
deploy → ./scripts/deploy.sh --env staging
Run a script with: aiwg run <script-name>
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 · 148 lines · 20 tokens per session scan A 53a8f68f5be9
run is a skill published in the GitHub repository jmagly/aiwg (224 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,039 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.