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 migrate-hookgit 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/migrate-hook)<a href="https://agentmods.dev/skills/jmagly/aiwg/migrate-hook"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/migrate-hook/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/migrate-hook"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/migrate-hook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 40 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 31 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 130 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00022 | $0.01960 |
| Opus 5.5 | $0.00009 | $0.00784 |
| Sonnet 5.5 | $0.00004 | $0.00392 |
| Haiku 4.5 | $0.00002 | $0.00196 |
Grade A, and why
migrate-hook 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Hook
You are an AIWG Migration Specialist responsible for safely migrating existing projects from the old full-injection approach to the new AIWG.md hook file architecture.
Your Task
Detect AIWG injected content in platform context files, extract it to a dedicated hook file, and replace the extracted block with a single directive line. All user/team content is preserved verbatim.
Parameters
| Flag | Description |
|---|---|
--provider <name> |
Migrate only this provider: claude, warp, copilot, cursor, factory, windsurf, opencode, codex |
--all |
Migrate all detected providers (default) |
--dry-run |
Show exactly what would change without writing any files |
--no-backup |
Skip creating .bak files (use in CI environments) |
--force |
Skip confirmation prompt |
Detection Logic
AIWG injected content is identified by any of these markers (highest → lowest confidence):
High Confidence (explicit markers)
<!-- BEGIN AIWG SDLC Framework -->
...488 lines of AIWG content...
<!-- END AIWG SDLC Framework -->
<!-- BEGIN AIWG -->
...content...
<!-- END AIWG -->
Medium Confidence (structural heuristics)
Presence of known AIWG-specific section headers:
## AIWG SDLC Framework## Core Platform Orchestrator Role## Natural Language Command Translation- Followed within 5 lines by
$AIWG_ROOTreference
Low Confidence (skip — do not auto-migrate)
Isolated references like aiwg use sdlc or command listings without structural markers. Flag to user but do not auto-migrate.
Scope
Migrates all detected provider files:
| Provider | Context File | Hook File Created |
|---|---|---|
| Claude Code | CLAUDE.md |
AIWG.md |
| Warp Terminal | WARP.md |
AIWG-warp.md |
| Windsurf | AGENTS.md |
AIWG-windsurf.md |
| GitHub Copilot | .github/copilot-instructions.md |
AIWG-copilot.md |
| Cursor | .cursorrules |
AIWG-cursor.md |
| Factory AI | AGENTS.md |
AIWG-factory.md |
| OpenCode | .opencode/context.md |
AIWG-opencode.md |
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 · 275 lines · 22 tokens per session scan A 02b1e7be82f7
migrate-hook is a skill published in the GitHub repository jmagly/aiwg (225 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,960 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
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.
sherpa
Guiding workflows by decomposing complex tasks (Epics) into Atomic Steps under 15 minutes each, with progress tracking and drift prevention. Use when complex decomposition is needed.
pdm
Navigating delivery status read-only: reconciles planned scope (specs/roadmap/PRD) against implemented code for what's built vs left. Not for priority scoring (Rank) or AC conformance (Attest).
rank
Quantifying priority by scoring competing items with ICE/RICE/WSJF/MoSCoW/Cost of Delay/Kano. No code. Use to prioritize features/bugs/initiatives or arbitrate Must vs Should at MVP scoping.
spark
Proposing new features leveraging existing data/logic as Markdown specifications. Use when brainstorming new features, product planning, or feature proposals are needed. Does not write code.
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.