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.00265 |
| Opus 5.5 | $0.00011 | $0.00106 |
| Sonnet 5.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 5d 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 --body. - 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.
- 5d ago Changed 7e7435f08a06
- 1mo 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 (225 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 265 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.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
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.
gh
Use when the user works with GitHub from the command line - listing or viewing pull requests, creating PRs and issues, reviewing or merging, watching workflow runs, downloading release assets, or hitting the REST/GraphQL API.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.