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.
/plugin marketplace add jmagly/aiwgnpx agentmods add plugins/jmagly/aiwg/marketplacegit 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/plugins/jmagly/aiwg/marketplace)<a href="https://agentmods.dev/plugins/jmagly/aiwg/marketplace"><img src="https://agentmods.dev/badge/plugins/jmagly/aiwg/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
aiwg marketplace 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 today.
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 — 703 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "aiwg",
"owner": {
"name": "AIWG Contributors",
"email": "[email protected]"
},
"description": "AIWG - Modular agentic framework for SDLC, marketing automation, and workflow orchestration. 200+ agents, 67+ CLI commands, 400+ deployable agent/skill/command/rule artifacts.",
"version": "2026.9.0",
"plugins": [
{
"name": "sdlc",
"source": "./agentic/code/plugins/sdlc",
"description": "Complete SDLC framework with 180+ specialized agents for software development lifecycle management.",
"version": "2026.9.0",
"author": {
"name": "AIWG Contributors"
},
"license": "MIT",
"category": "productivity",
"keywords": []
},
{
"name": "marketing",
"source": "./agentic/code/plugins/marketing",
"description": "Marketing automation framework with 37 specialized agents for campaign management.",
"version": "2026.9.0",
"author": {
"name": "AIWG Contributors"
},
"license": "MIT",
"category": "productivity",
"keywords": []
},
{
"name": "voice",
"source": "./agentic/code/plugins/voice",
"description": "Voice profile system for consistent, authentic writing.",
"version": "2026.9.0",
"author": {
"name": "AIWG Contributors"
},
"license": "MIT",
"category": "productivity",
"keywords": []
},
{
"name": "writing",
"source": "./agentic/code/plugins/writing",
"description": "Writing quality validation and AI pattern detection.",
"version": "2026.9.0",
"author": {
"name": "AIWG Contributors"
},
"license": "MIT",
"category": "productivity",
"keywords": []
},
{
"name": "utils",
"source": "./agentic/code/plugins/utils",
"description": "Core AIWG utilities for context regeneration and workspace management.",
"version": "2026.9.0",
"author": {
"name": "AIWG ConWhat 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.
- today Changed 36bcef1f3d89
- 4d ago First seen · 703 lines scan A e70b2848cde1
aiwg marketplace is a plugin published in the GitHub repository jmagly/aiwg (208 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-08-30.
Other plugins, from other repositories
nightshift
Keep long Claude Code runs on task: enforce the punch list, park questions, preserve progress, recover crashes, and run product or quality shifts until done.
claude-code-recap
Lists recent Claude Code sessions across every project with summaries, git branch, model, turn count, and a ready-to-paste resume command, and can re-open a whole working set in terminal tabs.
flow
The /flow engine — one unified, PM-agnostic workflow system spanning capture → done. Manual stages and an autonomous loop seated on DorkOS Pulse.
software-verification
Design verification strategies that unlock higher levels of autonomous software development.
catalyst-legacy
Pre-phase-agent (wave-based) orchestration workflow preserved as a documented fallback: oneshot, orchestrate, god, setup-orchestrate. Superseded by catalyst-dev's execution-core/phase-agent pipeline. Requires catalyst-dev (shared backing scripts).
pbr
Plan-Build-Run — Structured development workflow for Claude Code. Solves context rot through disciplined subagent delegation, structured planning, atomic execution, and goal-backward verification.