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 indexgit 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/index)<a href="https://agentmods.dev/skills/jmagly/aiwg/index"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/index.svg" alt="Measured on agentmods" 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.00031 | $0.02066 |
| Opus 5 | $0.00015 | $0.01033 |
| Sonnet 5 | $0.00006 | $0.00413 |
| Haiku 4.5 | $0.00003 | $0.00207 |
Grade A, and why
index 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 5d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Index
You manage the AIWG artifact index — building or rebuilding the searchable index of all SDLC artifacts in .aiwg/, querying it by text, inspecting dependency graphs, and reporting index statistics.
Scope: the JSON artifact graph AND research-corpus markdown views. This skill manages the JSON artifact graph under
.aiwg/.index/*(nodes, edges, checksums). As of #1490,aiwg index buildalso renders research-corpus markdown views (indices/by-topic.md,indices/by-year.md,indices/authors.md,citation-network, …) natively, in the same process — one command produces both from one config (.aiwg/aiwg.configindex.graphs, #1491). The former standalonecorpus-index-buildbuild.pyis retired; that skill now points back toaiwg index build. Markdown views render only when the project has adocumentation/references/corpus, so this is a no-op in ordinary SDLC projects.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "index my artifacts" → build
- "find requirements about authentication" → query "authentication"
- "what depends on UC-001" → deps .aiwg/requirements/UC-001.md
- "show neighboring artifacts" → neighbors --node
- "compare related artifacts" → set --op intersection --node-a --node-b
- "how many artifacts are indexed" → stats
- "is the index healthy" → status
- "export the index for Fortemi" → export --format fortemi
- "sync the Fortemi cache" → sync
- "refresh the index" → build --force
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Build index | "build the artifact index" | Run aiwg index build |
| Post-clone bootstrap | "I just cloned this, queries return nothing" / "the index is missing" | Run aiwg index build --all (the index is gitignored, not committed — see note below) |
| Force rebuild | "rebuild the index from scratch" | Run aiwg index build --force --verbose |
| Text search | "search artifacts for authentication" | Run aiwg index query "authentication" |
| Dependency graph | "show dependencies for the SAD" | Run aiwg index deps .aiwg/architecture/software-architecture-doc.md |
| Neighbor graph | "show related nodes for REF-001" | Run aiwg index neighbors --graph <name> --node REF-001 |
| Set operation | "what overlaps between these two nodes" | Run aiwg index set --graph <name> --op intersection --node-a <id> --node-b <id> |
| Statistics | "how many artifacts are indexed?" | Run aiwg index stats |
| Health/status | "is the index stale?" | Run aiwg index status --json |
| JSON output | "get index stats as JSON" | Run aiwg index stats --json |
| Fortemi export | "export this index for Fortemi" | Run aiwg index export --format fortemi --schema-version v2 |
| Fortemi cache | "sync the Fortemi Core index" | Run aiwg index sync |
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.
- 5d ago First seen · 194 lines · 31 tokens per session scan A cd6a0844e62b
index is a skill published in the GitHub repository jmagly/aiwg (209 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 2,066 once invoked, about $0.0002 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.