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-regenerate-warpgit 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-warp)<a href="https://agentmods.dev/skills/jmagly/aiwg/aiwg-regenerate-warp"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-regenerate-warp/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-warp"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-regenerate-warp.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.00019 | $0.01457 |
| Opus 5 | $0.00010 | $0.00728 |
| Sonnet 5 | $0.00004 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
aiwg-regenerate-warp 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regenerate WARP.md
Regenerate the WARP.md file for Warp Terminal integration, analyzing current project state while preserving team directives and organizational requirements.
Hook file approach (default): Generates AIWG-warp.md and adds a section or @AIWG-warp.md directive to WARP.md. Note: Warp's @-link support is unverified — defaults to section-style toggle until confirmed (see #444).
Full inject (--full-inject): Embeds AIWG content inline in WARP.md with AIWG markers.
Parameters
| Flag | Description |
|---|---|
--no-backup |
Skip creating backup file |
--dry-run |
Preview changes without writing |
--show-preserved |
List all detected preserved content and exit |
--full |
Full regeneration, preserve nothing (destructive) |
Warp Terminal Conventions
WARP.md follows Warp Terminal formatting conventions:
###headings for agents and commands (not##)- Inline tool lists with agents
- Terminal-friendly command formatting (easy copy-paste)
- Concise descriptions optimized for terminal display
Execution Steps
Step 1: Create Backup
Unless --no-backup specified:
- Check if
WARP.mdexists - If exists, copy to
WARP.md.backup-{YYYYMMDD-HHMMSS} - Report backup location
Step 2: Extract Preserved Content
Same preservation patterns as CLAUDE.md:
- Explicit Preserve Blocks:
<!-- PRESERVE -->...<!-- /PRESERVE --> - Preserved Section Headings: Team *, Org *, Definition of Done, etc.
- Inline Directives: Lines with directive keywords
Step 3: Analyze Project
Same project analysis as CLAUDE.md:
- Languages and package managers
- Development commands
- Test framework
- CI/CD configuration
- Directory structure
Step 4: Detect AIWG State
Check installed frameworks and deployed assets:
- Scan for WARP-specific formatting in existing files
- Count agents and commands
- Identify active frameworks
Step 5: Generate WARP.md
Document Structure (Warp Format):
# WARP.md
Project guidance for Warp Terminal AI assistance.
## Project Overview
{Brief project description from README.md}
**Tech Stack**: {languages} | **Package Manager**: {npm/pip/etc} | **Test Framework**: {framework}
## Quick Commands
Copy-paste ready commands for common tasks:
```bash
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 · 249 lines · 19 tokens per session scan A 3cc35d36fd24
aiwg-regenerate-warp is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,457 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.