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 hashiiiii/rules-for-ai --skill hashiiiii-pull-requestgit clone --depth 1 https://github.com/hashiiiii/rules-for-aiWrote 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/hashiiiii/rules-for-ai/hashiiiii-pull-request)<a href="https://agentmods.dev/skills/hashiiiii/rules-for-ai/hashiiiii-pull-request"><img src="https://agentmods.dev/badge/skills/hashiiiii/rules-for-ai/hashiiiii-pull-request/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/hashiiiii/rules-for-ai/hashiiiii-pull-request"><img src="https://agentmods.dev/badge/skills/hashiiiii/rules-for-ai/hashiiiii-pull-request.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.00028 | $0.00816 |
| Opus 5.5 | $0.00011 | $0.00326 |
| Sonnet 5.5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
hashiiiii-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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Conventions
Use the pull request structure from the repository. If the repository defines a structure, do not replace it.
Locale
Before you draft a pull request, resolve its language:
- If project instructions specify a pull request language, use that language.
- If project instructions do not specify a language, use the resolved
pull-requestskey from the context. - If the context has no resolved keys, read the first existing locale file.
- Use this file order: local, project, user, and bundled
LOCALE.default.md. - Use
<absolute-git-dir>/rules-for-ai/LOCALE.mdfor the local file. - Use
<repo>/.rules-for-ai/LOCALE.mdfor the project file. - Use
${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.mdfor the user file. - If no locale file exists, use
en_US. - Use the
pull-requestslanguage for the pull request title and body.
Use the exact section headings from the selected template. For the default structure, always write the headings in English.
If pull-requests is ja_JP, keep the English headings. Write the text below each heading in Japanese.
When to Use
- Before
gh pr create - Before you edit a pull request body with
gh pr edit --body - If the user asks you to draft a pull request
Repository Template (preferred)
Before you draft the body, search for a pull request template in this order:
.github/pull_request_template.md.github/PULL_REQUEST_TEMPLATE.mdpull_request_template.mdat the repository root- A single
.mdfile under.github/PULL_REQUEST_TEMPLATE/
If a template exists, read it. Use its headings, order, and subsections without changes.
Fill every Markdown ATX heading that the template defines (# through ######).
If the repository has multiple templates, use the template that the user or repository selects.
Default Template (fallback)
If the repository has no pull request template, use this structure:
## Summary
## Motivation
## Changes
## Testing
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.
- 1mo ago First seen · 103 lines · 28 tokens per session scan A 3194566f83fd
hashiiiii-pull-request is a skill published in the GitHub repository hashiiiii/rules-for-ai (10 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 816 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-08-31.
Other skills, from other repositories
issue-work-loop
Run Herdr loops for one open GitHub issue (resolve→review→fix) or an existing PR (review→lazy fixer) until CLEAN. Don't use for plain resolution without review, review-only/no-fix requests, backlog automation, or merging.
doris-repo-review
Review an Apache Doris PR from a local clone with the same multi-agent, shared-ledger convergence workflow as the CI Code Review Runner. Use when the user supplies a PR to /doris-repo-review, asks to review a Doris PR locally, or asks for the CI-style review flow. Safely align only the current worktree to the exact PR…
gh-address-comments
Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging…
review-pr
Forensic, stage-aware pull request review. Reconstructs the commit narrative, tests architectural premises against project reality, detects over-engineering, and produces a ready-to-post review comment. Use when the user says "review PR", "review this PR", "review PR #N", "is this PR ready to merge", "review the…
azure-repos
Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch policies/PR checks, TFVC→Git migrations, large files, or…
review
Review in three modes — code (diff vs standards/spec), design (NOTES + tech-spec before planning), drift (implementation vs tech-spec before ship). Pick mode from Flow Conductor phase or user intent; do not mix artifact types.