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 customize-rebuildgit 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/customize-rebuild)<a href="https://agentmods.dev/skills/jmagly/aiwg/customize-rebuild"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/customize-rebuild/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/customize-rebuild"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/customize-rebuild.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.00021 | $0.00899 |
| Opus 5 | $0.00010 | $0.00449 |
| Sonnet 5 | $0.00004 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
customize-rebuild 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customize Rebuild
You rebuild and redeploy AIWG from the user's local clone so their recent edits go live. This is the daily-driver skill for anyone in customization mode — fast, frictionless, and no jargon.
Triggers
- "apply my changes"
- "make this live" / "make it live"
- "rebuild" / "redeploy"
- "recompile"
- "push my edits live"
- "update my AIWG"
- "deploy my customizations"
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Apply changes | "apply my changes" | aiwg use all (fast path) |
| Full rebuild | "rebuild everything" | npm run build + aiwg use all |
| Redeploy workflow | "redeploy the current customizations" | Verify dev mode and build need, then use aiwg use all as the deployment step |
Behavior
When triggered:
-
Verify customization mode is active:
aiwg version # should show [dev] and the repo pathIf not in dev mode, tell the user and offer to run
customize-setup. -
Determine whether a TypeScript build is needed:
- Check if any
.tsfiles changed since last build:git -C <edgePath> diff --name-only HEAD -- src/ '*.ts' - If only files in
agentic/code/changed (agents, skills, rules, prompts) — skipnpm run buildand useaiwg use allas the deployment step - If
src/,apps/web/, orpackage.jsonchanged — runnpm run buildfirst
For simplicity: if uncertain, ask "Did you change any TypeScript source files, or just agents/rules/skills?" and act accordingly. Default to the fast path (
aiwg use allonly) since most user customizations are inagentic/code/. - Check if any
-
Fast path (most common — editing agents, rules, skills):
aiwg use all -
Full rebuild path (when TS source changed):
npm --prefix <edgePath> run build aiwg use all -
Report result concisely:
Done — deployed X agents, Y skills, Z rules from ~/my-aiwg. Changes are live in your next session.
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 · 102 lines · 21 tokens per session scan A 239717cfddc9
customize-rebuild is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 899 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
autoship
Runs a changesets npm release through the version PR, CI publish, and registry verification. Use when asked to "release this package", "autoship", "merge Version Packages", or diagnose a release that did not publish. For feature PRs use pr-creator or pr-babysitter.
fest-execution
Execute active festival tasks. Use when finding the next task, marking tasks completed/blocked/reset, committing with festival traceability, advancing workflow steps, and validating sequence progress.
sync-references
Pull latest changes from origin for all git repos under a directory. Use when asked to update, sync, or pull reference projects.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
publish
Bump version, build, test, publish to npm, and install locally.