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 ALTEN-group/coding-pal --skill pr-recordgit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/pr-record)<a href="https://agentmods.dev/skills/alten-group/coding-pal/pr-record"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/pr-record/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/alten-group/coding-pal/pr-record"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/pr-record.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.00075 | $0.00641 |
| Opus 5.5 | $0.00030 | $0.00256 |
| Sonnet 5.5 | $0.00015 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
pr-record 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 4d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Record
Make the pull request a deterministic record: what it closes, which criteria it proves, which dependencies it adds, how risky it is, and who validated it. AI opens it with Human Validation Pending; people validate it in Prove.
When to Use This Skill
- A Code agent finished all plan steps and must open the pull request.
- CI must gate the pull request before Prove (
--stage code). - CI or a maintainer must check the human validation record before merge (
--stage prove).
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/pr-record/ or .claude/skills/pr-record/, use that base path. Run the scripts from the repository root (so specs/ paths resolve) and write <skill-dir> as that install path.
Workflow
- Read
references/pr-record-contract.mdnow. It is the authoritative source for the body sections, the Human Validation fields, and the required validators per blast radius tier. - Install
references/pull_request_template.mdas.github/pull_request_template.mdonce per repository, and customise it. - Write the body from the work item: the links, one traceability row per acceptance criterion with its test, the dependencies declared in the plan, the tier and rollback from
think.md. Leave every Human Validation fieldPending. - Validate from the repository root:
# Code exit gate (agent)
node <skill-dir>/scripts/validate-pr.mjs --body pr.md --dir specs/issue-42 --stage code --added-deps "zod"
# Prove human validation record (people)
node <skill-dir>/scripts/validate-pr.mjs --body pr.md --dir specs/issue-42 --stage prove --pr-date 2026-10-13
Treat a nonzero exit as an invalid pull request and fix the body. --stage code also needs a plan approved by a named Developer; the agent never fills in that approval. Never fill Human Validation as an agent, and never claim a line-by-line review.
What ships with it
5 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.
- 4d ago First seen · 43 lines · 75 tokens per session scan A 027c92669bad
pr-record is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 75 tokens to every session and 641 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
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.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…