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 aiwg-regenerategit 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/aiwg-regenerate)<a href="https://agentmods.dev/skills/jmagly/aiwg/aiwg-regenerate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-regenerate/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/aiwg-regenerate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-regenerate.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.00023 | $0.00724 |
| Opus 5 | $0.00012 | $0.00362 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
aiwg-regenerate 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regenerate Context — Branch Selector
The CLI is the deterministic source of truth for context regeneration. An
unqualified invocation previews transactional adoption for an established,
not-yet-extracted repository; fresh or already-adopted projects route to the
canonical refresh. Mutation of an inferred adoption always requires an explicit
--apply. Do not make users choose a branch unless they want to override the
selection.
Select and load exactly one linked branch before execution:
- Canonical workspace graph — default refresh for new and already-migrated projects.
- Existing-project extraction —
transactional adoption of stable project metadata and provider context into
the canonical graph; preview is the default and
--applyis required. - Legacy full injection — compatibility branch; embeds normalized AIWG context inside the provider startup file.
Commands
# Intelligent default (recommended user surface)
aiwg run skill aiwg-regenerate
# Canonical default
aiwg regenerate --workspace [--provider <name>] [--dry-run] [--force]
# Existing-project transactional adoption
aiwg regenerate --existing-project [--provider <name>] [--dry-run|--apply]
# Legacy compatibility
aiwg regenerate --full-inject [--provider <name>] [--dry-run]
--legacy aliases --full-inject. The CLI rejects conflicting branches,
unknown options, and missing provider values with usage status.
--existing-project rejects --force and all --no-*-md partial-write flags.
It refuses possible credentials and ambiguous directive conflicts, previews the
exact extracted block and transaction targets, and prints the rollback command
after apply.
Explicit branch flags always win. Without one, the executable selector checks
the canonical extractor's complete stable-source inventory and managed markers.
A first-time established project is previewed; rerun with --apply to adopt it.
An already-extracted or genuinely signal-free project uses --workspace.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 78 lines · 23 tokens per session scan A 46cbad065150
aiwg-regenerate is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 724 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
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
goal-writer
Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user says "draft a goal", "write a goal+rider"…
horizon
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
check-in
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
hyperplan
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.