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 plugin-statusgit 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/plugin-status)<a href="https://agentmods.dev/skills/jmagly/aiwg/plugin-status"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/plugin-status/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/plugin-status"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/plugin-status.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.00018 | $0.00996 |
| Opus 5 | $0.00009 | $0.00498 |
| Sonnet 5 | $0.00004 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
plugin-status 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Status
You list installed Claude Code marketplace plugins with their version, install date, and enabled status. In AIWG vocabulary, these are delivery wrappers around extension, addon, or framework payloads.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "what's installed?" → show all plugins
- "do I have the voice plugin?" → check if specific plugin is installed
- "is the SDLC plugin up to date?" → show installed version vs latest
- "what plugins does this project use?" → show plugin status
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Status request | "plugin status" | Run aiwg plugin-status |
| List request | "show plugins" | Run aiwg plugin-status |
| List all | "list plugins" | Run aiwg plugin-status |
| What's installed | "what plugins are installed" | Run aiwg plugin-status |
| Check specific | "is voice@aiwg installed?" | Run aiwg plugin-status voice@aiwg |
| JSON output | "plugin status as JSON" | Run aiwg plugin-status --json |
| Outdated check | "are any plugins outdated?" | Run aiwg plugin-status --check-updates |
Behavior
When triggered:
-
Extract intent:
- Is a specific plugin being queried, or is this a full list?
- Is the user checking for outdated versions?
- Is machine-readable output needed?
-
Run the appropriate command:
# List all installed plugins aiwg plugin-status # Check a specific plugin aiwg plugin-status sdlc@aiwg # Check for available updates aiwg plugin-status --check-updates # Machine-readable JSON output aiwg plugin-status --json -
Report the result — show package name, version, install date, enabled status, and update availability.
Output Format
Installed Marketplace Packages (2)
sdlc@aiwg
Version: 2026.3.15
Installed: 2026-03-28
Status: enabled
Update: none (latest)
voice@aiwg
Version: 2026.2.10
Installed: 2026-02-14
Status: enabled
Update: 2026.3.15 available — run `aiwg install-plugin voice@aiwg --force`
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 · 136 lines · 18 tokens per session scan A 6921da3448f6
plugin-status is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 996 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
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.