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-doctorgit 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-doctor)<a href="https://agentmods.dev/skills/jmagly/aiwg/aiwg-doctor"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-doctor/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-doctor"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-doctor.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.00025 | $0.01093 |
| Opus 5 | $0.00013 | $0.00547 |
| Sonnet 5 | $0.00005 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
aiwg-doctor 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 8d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWG Doctor
You run a comprehensive health check on the AIWG installation and workspace, reporting pass/fail for each diagnostic with remediation steps for any failures.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "is aiwg healthy" → run
aiwg doctor - "something is broken" → run
aiwg doctorto isolate the issue - "aiwg isn't working" → run
aiwg doctor - "check my aiwg setup" → run
aiwg doctor - "run diagnostics" → run
aiwg doctor - "aiwg broken" → run
aiwg doctor
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Health check | "check health" / "is aiwg healthy" | Run aiwg doctor |
| Diagnostic request | "diagnose" / "run diagnostics" | Run aiwg doctor |
| Broken install | "aiwg isn't working" | Run aiwg doctor |
| Setup validation | "check my aiwg setup" | Run aiwg doctor |
| Troubleshooting | "troubleshoot installation" | Run aiwg doctor |
| Verbose check | "run full diagnostics" | Run aiwg doctor --verbose |
Behavior
When triggered:
-
Extract intent:
- Is this a routine check or is the user reporting a specific problem?
- Did the user mention a symptom (e.g. "commands not found", "frameworks missing")? If so, note it to help interpret the doctor output.
- Does the user want verbose output?
-
Run the appropriate command:
# Standard health check aiwg doctor # Verbose output (additional detail per check) aiwg doctor --verboseThe doctor command (
tools/cli/doctor.mjs) validates:- npm package is installed and executable
.aiwg/frameworks/registry.jsonexists and is valid JSON- Framework files are deployed to the active platform directories (e.g.
.claude/agents/,.claude/commands/) - Node.js version meets minimum requirements
- Required tools are available (
git,node,npm) - Channel configuration is consistent
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.
- 8d ago First seen · 133 lines · 25 tokens per session scan A 535fd9d98e53
aiwg-doctor is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,093 once invoked, about $0.0001 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
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
parallax-core
Apply session-safe Parallax reasoning and verification to code changes.
typescript-circular-dependency
Detect and resolve TypeScript/JavaScript circular import dependencies. Use when: (1) "Cannot access 'X' before initialization" at runtime, (2) Import returns undefined unexpectedly, (3) "ReferenceError: Cannot access X before initialization", (4) Type errors that disappear when you change import order, (5) Jest/Vitest…
nextjs-server-side-error-debugging
Debug getServerSideProps and getStaticProps errors in Next.js. Use when: (1) Page shows generic error but browser console is empty, (2) API routes return 500 with no details, (3) Server-side code fails silently, (4) Error only occurs on refresh not client navigation. Check terminal/server logs instead of browser for…
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…