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-setupgit 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-setup)<a href="https://agentmods.dev/skills/jmagly/aiwg/customize-setup"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/customize-setup/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-setup"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/customize-setup.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.00033 | $0.01366 |
| Opus 5.5 | $0.00013 | $0.00546 |
| Sonnet 5.5 | $0.00007 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
customize-setup 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customize Setup
You set up AIWG in personal customization mode — where a local clone or fork of the AIWG repo becomes the user's global AIWG instance. Any edits they make to that clone go live on next rebuild.
This is the ownership story, not the developer/contributor story. Frame everything around "make it yours," not "build for the repo."
Triggers
- "set up AIWG customization mode"
- "I want to customize AIWG live"
- "make AIWG mine" / "make it mine"
- "set up my personal AIWG"
- "fork and customize AIWG"
- "I want to edit my agents and rules"
- "how do I customize AIWG?"
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Fork path | "set up AIWG with my own fork" | gh fork + clone + dev mode |
| Clone path | "clone AIWG so I can customize it" | git clone + dev mode |
| From existing clone | "I already cloned AIWG, set it up" | Just run dev mode + deploy |
| Vague customization | "I want to tweak my AIWG setup" | Ask fork or clone, then proceed |
Behavior
When triggered:
-
Ask one question (if not already clear from context):
"Do you want to fork AIWG on GitHub first (recommended — keeps your changes safe when upstream releases), or just clone it locally to get started?"
- Fork: user gets their own copy on GitHub, upstream sync works, can PR back
- Clone: fastest start, no upstream sync later
-
Determine target path — ask where to put the clone (default:
~/my-aiwg):"Where should I clone it? (default: ~/my-aiwg)"
-
Execute the appropriate path:
Fork Path
Requires gh CLI logged into GitHub.
# Fork jmagly/aiwg to user's GitHub account + clone + set upstream remote
gh repo fork jmagly/aiwg --clone --remote --clone-dir ~/my-aiwg
# Switch AIWG to use this fork as the global source
aiwg --use-dev ~/my-aiwg
# Build (compiles TypeScript + web app)
npm --prefix ~/my-aiwg run build
# Deploy from local source
aiwg --prefix ~/my-aiwg use all
Verify remotes after fork:
cd ~/my-aiwg && git remote -v
# origin https://github.com/USER/aiwg.git (their fork)
# upstream https://github.com/jmagly/aiwg.git (canonical)
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 · 151 lines · 33 tokens per session scan A ec40cff220cf
customize-setup is a skill published in the GitHub repository jmagly/aiwg (226 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,366 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-09-03.
Other skills, from other repositories
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.
launch
Planning releases and reporting delivery work from GitHub PR history. Use when versioning, CHANGELOGs, rollout or rollback plans, engineering metrics, retrospectives, or stakeholder reports are needed.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
trail
Investigating git history, analyzing regression root causes, and performing code archaeology. Time-travels through commits to uncover truth. Use for git history investigation.
oss-repo-maintainer
Maintain open-source repositories by checking README accuracy, version consistency, release readiness, and documentation drift. Use for: fix README, prepare release, repository maintenance, sync documentation.
missive
Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.