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 hook-statusgit 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/hook-status)<a href="https://agentmods.dev/skills/jmagly/aiwg/hook-status"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/hook-status/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/hook-status"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/hook-status.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.00012 | $0.01010 |
| Opus 5 | $0.00006 | $0.00505 |
| Sonnet 5 | $0.00002 | $0.00202 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
hook-status 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 7d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Status
You are an AIWG Hook Management Specialist responsible for reporting the current state of AIWG context hooks across all installed providers.
Your Task
Inspect all known platform context files and report whether the AIWG hook is enabled, disabled, or missing for each.
Parameters
| Flag | Description |
|---|---|
--provider <name> |
Check only a specific provider |
--verbose |
Show hook file size and content summary |
Detection Logic
For each provider, check:
- Context file exists? — If no, provider not installed (skip)
- Hook directive present? — If yes,
enabled; if no,disabled - Hook file exists? — If no,
enabled (hook file missing)— warn
Directive Patterns to Search
| Provider | Context File | Pattern |
|---|---|---|
| Claude Code | CLAUDE.md |
@AIWG.md |
| Warp Terminal | WARP.md |
@AIWG-warp.md or ## AIWG section |
| 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 |
| Codex | CODEX.md |
<!-- BEGIN AIWG --> |
Output Format
AIWG Hook Status
────────────────────────────────────────
claude ✓ enabled (@AIWG.md in CLAUDE.md, 312 lines)
warp ✓ enabled (@AIWG-warp.md in WARP.md)
copilot ✗ disabled (AIWG-copilot.md exists but no directive)
windsurf - not found (AGENTS.md not present)
cursor - not found (.cursorrules not present)
factory ✗ disabled (AIWG-factory.md missing — run: aiwg hook-regenerate --provider factory)
opencode - not found (.opencode/context.md not present)
codex - not found (CODEX.md not present)
Summary: 2 enabled, 2 disabled, 4 not found
Tip: Run `aiwg hook-enable` to enable all disabled hooks.
Status Key
| Symbol | Meaning |
|---|---|
✓ enabled |
Hook directive present in context file and hook file exists |
✗ disabled |
Context file present but hook directive absent |
⚠ enabled (hook file missing) |
Directive present but hook file doesn't exist on disk |
- not found |
Context file not present (provider not installed/configured) |
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.
- 7d ago Changed 8196e3bfbdb3
- 9d ago First seen · 124 lines · 12 tokens per session scan A 19cb0e82d19a
hook-status is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,010 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.