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 niels-emmer/myace --skill pr-standardsgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/pr-standards)<a href="https://agentmods.dev/skills/niels-emmer/myace/pr-standards"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/pr-standards/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/niels-emmer/myace/pr-standards"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/pr-standards.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.00529 |
| Opus 5.5 | $0.00010 | $0.00212 |
| Sonnet 5.5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
PR Standards 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.
What it actually says
Purpose
A PR is the unit of review. A good description makes review fast and safe; a thin one makes reviewers guess at intent. This skill standardizes the description, the review depth, and the merge gate so nothing important is left to chance — and so a reviewer can verify the change matches its stated intent rather than trusting the summary.
When to use it
Any time you open, review, or merge a pull request.
PR description template
## Summary
<!-- One paragraph: what changed and why. -->
## Related issues
<!-- Closes: #N, Refs: #M -->
## Type of change
- [ ] feat (new feature)
- [ ] fix (bug fix)
- [ ] refactor (no behaviour change)
- [ ] test (tests only)
- [ ] docs (documentation)
- [ ] chore (tooling, deps, CI)
- [ ] security (security hardening)
## Testing
<!-- How was this tested? Commands run, manual steps, edge cases checked. -->
## Checklist
- [ ] Self-review completed
- [ ] Tests pass
- [ ] No secrets in the diff
- [ ] Docs updated if behaviour changed
Review depth
- Read the diff, not just the description — verify the change matches the stated intent.
- Check for behavioural regressions, missing verification, and scope creep (unrelated changes sneaking in).
- For security-sensitive changes (auth, payments, data access, crypto), require a dedicated security review, not just a general pass.
- Leave concrete, actionable feedback; approve only when you'd be comfortable owning the change.
Merge gate
- At least one approving review before merging to a protected branch.
- Stale reviews are dismissed when new commits are pushed — re-review after changes.
- CI must pass before merge.
- Prefer squash or rebase merge for a clean history; avoid merge commits on a linear-history branch.
Expected output
A PR that a reviewer can understand and verify from the description alone, reviewed to a depth proportional to its risk, and merged only when it passes the gate.
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 · 62 lines · 25 tokens per session scan A 448bf9de883f
PR Standards is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 529 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
speclite-goal-orchestrator-epic-story-code-review-runner
An Epic Story code-review runner coordinates development and code review for Stories within an Epic. It moves one Story at a time through development, review, evaluation, fixes, verification, and closeout using structured records.
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
ase-repo-review
Perform a holistic, human-reviewer-style critique of the currently staged Git changes (or, with --unstaged, of the unstaged and untracked changes, with --branch, of a branch against its base, or, with --commit, of a single commit) and emit an approve/reject verdict with prioritized, severity-tagged, line-cited…
loom-git-workflow
Git operations guidance including branching strategies, commit conventions, merge workflows, conflict resolution, and worktree management.