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-delivery-prgit 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-delivery-pr)<a href="https://agentmods.dev/skills/jmagly/aiwg/aiwg-delivery-pr"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-delivery-pr/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-delivery-pr"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/aiwg-delivery-pr.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.00027 | $0.00263 |
| Opus 5 | $0.00014 | $0.00131 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
aiwg-delivery-pr 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 8d 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.
What it actually says
AIWG Delivery Pull Requests
Use this skill only for AIWG product/workspace delivery where .aiwg/aiwg.config delivery policy, AIWG issue linking, no-attribution, and CI-green-before-done rules are authoritative.
This is an explicit alias for aiwg-pr. Existing aiwg-pr callers remain valid. Generic requests like "open a PR for this repo" should use the host repository's normal PR tooling and templates, not this AIWG-specific workflow, unless the repository is the AIWG product workspace or the operator explicitly asks for AIWG delivery policy.
Route
- Read
aiwg-prwithaiwg show skill aiwg-pr. - Apply its delivery-policy and shared threat-assessment gates exactly.
- If the request is generic repository PR work, stop and route to ordinary git/Gitea/GitHub PR creation instead.
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.
- 8d ago First seen · 24 lines · 27 tokens per session scan A 9d0a581537a6
aiwg-delivery-pr is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 263 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
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
ship
Ship a feature branch end-to-end: merge target → test → review → version/changelog → commit → push → PR, then drive CI green and hand off the PR. Use after vd:cook when the branch is implemented and tested, ready to land on main/master (official), staging/uat (staging), or dev/beta (beta). Merge is opt-in - a bare…
capture-lessons
Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.