AIRI is a self-hosted virtual AI companion that gives an AI character a voice, visual presence, memory, and the ability to interact with games and coding activity. People use it as a personal digital companion on the web, macOS, or Windows, including for voice chat and gameplay. The catalogue add-ons provide workflows for working with the AIRI project.
Borrowing it
Nothing to install: this file belongs to moeru-ai/airi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moeru-ai/airi/main/.agents/skills/create-pr/SKILL.mdgit clone --depth 1 https://github.com/moeru-ai/airiWrote 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/moeru-ai/airi/create-pr)<a href="https://agentmods.dev/skills/moeru-ai/airi/create-pr"><img src="https://agentmods.dev/badge/skills/moeru-ai/airi/create-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/moeru-ai/airi/create-pr"><img src="https://agentmods.dev/badge/skills/moeru-ai/airi/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00045 | $0.01929 |
| Opus 5.5 | $0.00018 | $0.00772 |
| Sonnet 5.5 | $0.00009 | $0.00386 |
| Haiku 4.5 | $0.00005 | $0.00193 |
Grade A, and why
create-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 2d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Create a reviewable PR from the exact commits intended for publication. The PR body must explain the changed system, not only list changed files.
Workflow
- Inspect the repository instructions, status, branch, remotes, and target branch.
- Compute the merge base. Record the exact
base...headcomparison that the PR will publish. - Detect stacked work. Separate inherited changes from this PR's own changes.
- Review the complete diff. Trace changed files to their entry points, callers, state owners, persistence, and external boundaries.
- Classify the PR as a feature, fix, refactor, maintenance change, or a combination. Select context evidence that helps reviewers understand this change.
- Run checks that match the changed surfaces. Run the tests of the branch changes, as
AGENTS.mddescribes. Satisfy the repository's required final checks. - If the diff changes user-visible UI, follow the visual-evidence workflow below.
- Read the PR body template. Compose the body from verified code and runtime evidence.
- Publish the intended commits through the available GitHub or
ghworkflow. - Create the PR. Then open it and verify the title, base, head, body, diagrams, tables, and image Markdown.
- Get the PR review threads, comments, and check status. Fix each confirmed error and run focused checks.
- Push each correction. Reply with evidence and resolve the applicable thread.
Context Evidence
Build a small context brief before you write the PR body. Keep the analysis read-only until the normal publication step.
- Record the repository, target branch, head branch, merge base, and inspected commit range.
- For a stacked PR, identify the parent PR or branch. Do not describe inherited changes as this PR's own changes.
- Separate runtime code from generated files, lockfiles, snapshots, and migrations.
- Trace the changed files to real module boundaries. Include entry points, composition roots, protocols, domain services, persistence, adapters, and callers when applicable.
- Support architecture claims with file paths or symbols. Mark an unproven business intent as an assumption or an open question.
- Do not expose tokens, secrets, full user records, or webhook payloads.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed 8d8adc631469
- 1mo ago Changed · -26 lines 05f9b8c0fdaf
- 1mo ago Changed · +88 lines · -6 tokens per session 06d547d6f010
- 1mo ago Changed 1fdc58f92bc8
- 1mo ago Changed · +1 lines b754cdd8e49b
- 1mo ago First seen · 60 lines · 51 tokens per session scan A 9757649f033b
create-pr is a skill published in the GitHub repository moeru-ai/airi (50,636 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,929 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…