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 agentmods add skills/waniwani-ai/sdk/pull-requestnpx skills add WaniWani-AI/sdk --skill pull-requestgit clone --depth 1 https://github.com/WaniWani-AI/sdkWrote 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/waniwani-ai/sdk/pull-request)<a href="https://agentmods.dev/skills/waniwani-ai/sdk/pull-request"><img src="https://agentmods.dev/badge/skills/waniwani-ai/sdk/pull-request.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00068 | $0.00585 |
| Opus 5 | $0.00034 | $0.00293 |
| Sonnet 5 | $0.00014 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
pull-request 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Pull Request
Create a GitHub pull request immediately using the following rules:
Step 1: Ensure a Linear ticket exists (do this BEFORE pushing)
- Check whether a Linear ticket is already associated with this work. Look for a ticket identifier (e.g.
WAN-123) in the current branch name and in the latest commit message(s). - If a ticket identifier is found, reuse it - no need to create a new one.
- If NO ticket is found, create one with the Linear MCP:
- Do NOT hardcode an email. The Linear MCP is authenticated as the person running this skill, so assign the issue with
assignee: "me"- this is the reliable team-safe way to assign to the current user. (Git/GitHub email may differ from the Linear email, so matching by email is unreliable; only fall back tolist_usersmatching if"me"is unavailable.) Uselist_teamsto resolve the team. - Create the issue with a concise title derived from the latest commit message, assigned to
"me". - Set its state to "In Progress".
- Capture the returned ticket identifier (e.g.
WAN-123) and its URL. - Verify the assignment took effect (the created issue's
assigneeshould be the current user); if it didn't, retry the assignment explicitly withsave_issue.
- Do NOT hardcode an email. The Linear MCP is authenticated as the person running this skill, so assign the issue with
Step 2: Create the PR
- Push any uncommitted changes first if needed. If there are uncommitted changes, commit them first before creating the PR.
- Ensure we're on the correct branch (not main/master).
- Use
gh pr create --assignee @meto create the PR and auto-assign it to the user. - Use the latest commit message as the PR title.
- Make sure the Linear ticket is referenced so Linear links and auto-closes the PR: include the ticket identifier (e.g.
WAN-123) either in the branch name or in the PR description body. If the ticket identifier is NOT already in the branch name, the PR body MUST contain a lineCloses WAN-123(using the real identifier). If it is already in the branch name, leave the body empty.
Important:
- Keep the PR title simple - just use the commit message as-is.
- Do not add extra formatting or emoji to the title.
- The Linear ticket check/creation MUST happen before pushing.
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 First seen · 34 lines · 68 tokens per session scan A f39d9b76298c
pull-request is a skill published in the GitHub repository WaniWani-AI/sdk (17 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 585 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
codexless-release-supervisor
Prepare, validate, and publish Codexless preview/hotfix releases from the canonical household source, including acceptance anti-omission gates, candidate provenance/parity, manifest/build identity, native Windows/macOS fresh-install acceptance from clean public source, safe Git integration, GitHub prerelease…
codexless-browser-repair
Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working. Use for current-version Codexless Browser compatibility drift, not ordinary website bugs, general Browser operation, Codexless install/update work, or long-term…
squeeze-page-builder
Build email capture landing pages (squeeze pages) as single self-contained HTML files. Triggers on: "build a squeeze page", "email capture page", "lead magnet page", "create an opt-in page", "build an email list page", "lead capture landing page", "create a freebie page", "build a page to collect emails", "opt-in…
codex-with-chatgpt
Use ChatGPT (web) as the planning and review brain for Codex coding sessions, while Codex keeps full execution ownership. Use when the user says "使用 Codex with ChatGPT ..." / "Set up Codex with ChatGPT" / "用 ChatGPT 规划", when they ask to connect ChatGPT to the current workspace, disconnect it, or run a task through…
threebrowser-studio-mcp
Author, inspect, render, validate, animate, and save Three.js WebGPU projects in the native ThreeBrowser Studio through its real threestudio MCP tools. Use whenever Codex is asked to build or edit a ThreeBrowser Studio scene, material, Blender-style shader or texture graph, animation, lighting setup, camera, or…
add-widget
Add a new widget (React UI + MCP tool) to this template. Use when asked to "add a widget", "add a new tool with UI", "create a new widget", "scaffold a widget", or "build a new MCP App feature".