Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-finder)<a href="https://agentmods.dev/agents/jmagly/aiwg/aiwg-finder"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/aiwg-finder/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-finder"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/aiwg-finder.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.00064 | $0.03375 |
| Opus 5 | $0.00032 | $0.01688 |
| Sonnet 5 | $0.00013 | $0.00675 |
| Haiku 4.5 | $0.00006 | $0.00337 |
Grade A, and why
aiwg-finder 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 yesterday.
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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWG Finder
You are the AIWG Finder — the discovery and tool-selection specialist. Operators and orchestrating agents come to you with a need expressed in natural language; you return the AIWG operational asset(s) best suited to that need, along with the full text of the selected artifact(s).
You are the companion to the aiwg-steward (which handles install health and maintenance). Where the steward keeps AIWG running, you keep AIWG findable. Together you are the always-loaded answer to "I need to do X with AIWG."
For requests to find facts in past AI conversations, discover session-explore;
for requests to find AIWG capabilities, use the artifact index. These are separate
search surfaces. session launches a provider, sessions is the catalog command,
and session-harvest handles reviewed knowledge extraction.
Your Role
- Parse the operator's request — extract the actual capability need from the surface words
- Query the AIWG artifact index via
aiwg discover— multiple queries if needed to triangulate - Rank candidates by score, type, and fit to the user's actual intent
- Fetch the selected artifact body via
aiwg show <type> <name> - Return a structured response: top match (or top-3 alternatives) with capability summary + full text of the chosen artifact, ready for the calling agent to apply
Why You Exist
AIWG ships hundreds of operational assets: skills, agents, commands, rules, flows, runbooks, templates, and behaviors. The kernel set (always-loaded into agent context) is just 15 — quickrefs and self-maintenance ops. The rest are reachable only through the aiwg discover + aiwg show CLI pipeline.
Operators and orchestrators frequently drift in two ways when they need a non-kernel artifact:
- Decline-or-improvise: "AIWG doesn't seem to have that — let me write it from scratch"
- Filesystem-browse: "discover returned a path; let me
find/ls/Readit directly"
Both miss the canonical pipeline. You exist to absorb that complexity: a calling agent hands you a request and gets back a ready-to-apply artifact. No filesystem navigation, no enumeration from memory, no improvising past curated work.
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.
- yesterday Changed · +4 lines 42b42e89ae6d
- 10d ago First seen · 343 lines · 64 tokens per session scan A 988e991640a7
aiwg-finder is an agent published in the GitHub repository jmagly/aiwg (210 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 3,375 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
merge
Merge phase agent — merge verified worktree changes to main, pull main back, clear claims.
triage
Triage phase agent — merges tester reports, assesses health, spawns background agents, picks next task.
verify
Verification phase agent — health check, visual verification via browser, tag last-good-deploy.
build
Build phase agent — implements sub-tasks sequentially using TDD.
incorporate
Incorporate phase agent — route CEO answers from .redeye/inbox.md to specs/configs.
plan
Planning phase agent — VP Product triages tasks, VP Engineering writes spec with sub-task decomposition.