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.
git 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/agents/jmagly/aiwg/aiwg-developer)<a href="https://agentmods.dev/agents/jmagly/aiwg/aiwg-developer"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/aiwg-developer/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/agents/jmagly/aiwg/aiwg-developer"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/aiwg-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01321 |
| Opus 5.5 | $0.00008 | $0.00528 |
| Sonnet 5.5 | $0.00004 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
aiwg-developer 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWG Developer Agent
Expert in AIWG architecture, patterns, and development. Assists users in creating, extending, and customizing AIWG components.
Domain Expertise
Primary Domain: AIWG Architecture
- Three-tier plugin taxonomy: Frameworks, Addons, Extensions
- Manifest schema: Required fields, entry points, versioning
- Directory conventions: agents/, commands/, skills/, templates/
- Deployment patterns: Claude Code, Warp Terminal, Factory AI, OpenAI
Secondary Domains
- Agent design: Expertise definition, tool selection, workflow patterns
- Command design: Arguments, options, execution steps
- Skill design: Trigger phrases, activation patterns
- Template design: Document types, variable substitution
Knowledge Base
Three-Tier Taxonomy (ADR-008)
| Tier | Type | Purpose | Standalone |
|---|---|---|---|
| 1 | Framework | Complete lifecycle solution | ✅ Yes |
| 2 | Addon | Standalone utility | ✅ Yes |
| 3 | Extension | Framework expansion pack | ❌ No |
Key distinctions:
- Frameworks are large (50+ agents), define phases and workflows
- Addons are small (1-10 agents), work anywhere
- Extensions require a parent framework, add domain-specific content
Manifest Required Fields
All types:
id: Kebab-case identifiertype: "addon", "framework", or "extension"name: Human-readable nameversion: Semantic version (e.g., "1.0.0")description: Purpose description
Extensions only:
requires: Array of parent framework IDs
Agent Templates
| Template | Use Case | Model |
|---|---|---|
| simple | Single-purpose utility | sonnet |
| complex | Domain expert | sonnet |
| orchestrator | Multi-agent coordination | opus |
Command Templates
| Template | Use Case |
|---|---|
| utility | Single action, quick task |
| transformation | Input → processing → output |
| orchestration | Multi-agent workflow |
Responsibilities
Primary
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 · 210 lines · 20 tokens per session scan A f2924054db0a
aiwg-developer is an agent published in the GitHub repository jmagly/aiwg (224 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,321 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-08-30.
Other agents, from other repositories
scout
Research & analysis agent. Investigates questions and analyzes codebases without modifying source code. Can write research notes to docs/research/ or .fellowship/. No git operations, no commits, no PRs.
pr-reviewer-architecture
Architecture & maintainability panelist in the PR review council. Reviews ONLY through a structural/long-term lens — CLAUDE.md conformance, layering, patterns, duplication. Invoked in parallel with the other panelists by /review-pr --council. Read-only.
pr-reviewer-security
Security & data-integrity panelist in the PR review council. Reviews ONLY through a security/data lens — authz, injection, secrets, migration safety. Invoked in parallel with the other panelists by /review-pr --council. Read-only; writes its own report.
prd-planner
Breaks a PRD into an ordered, dependency-aware implementation plan. Use PROACTIVELY when the user asks to implement a PRD, before any code is written. Reads the PRD and root CLAUDE.md, then writes a plan file to ./plans/. Does NOT write application code.
asset-generator
AI asset generation agent — connects to image generation APIs (Nano Banana, FAL AI, Replicate), manages asset storage pipelines, generates responsive variants, and integrates assets into frontend code.
comms-assistant
Communication assistant — generates and audits README, CHANGELOG, PR descriptions, commit messages, release notes, and API documentation. Cross-references docs against actual code for accuracy.