Borrowing it
Nothing to install: this file belongs to Kemetra/Seshat-BI. 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/Kemetra/Seshat-BI/main/.claude/skills/pr-readiness-reviewer/SKILL.mdgit clone --depth 1 https://github.com/Kemetra/Seshat-BIWrote 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/kemetra/seshat-bi/pr-readiness-reviewer)<a href="https://agentmods.dev/skills/kemetra/seshat-bi/pr-readiness-reviewer"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/pr-readiness-reviewer/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/kemetra/seshat-bi/pr-readiness-reviewer"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/pr-readiness-reviewer.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.00244 | $0.04327 |
| Opus 5 | $0.00122 | $0.02164 |
| Sonnet 5 | $0.00049 | $0.00865 |
| Haiku 4.5 | $0.00024 | $0.00433 |
Grade A, and why
pr-readiness-reviewer 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 11d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-readiness-reviewer
Module Contract -- PR Readiness Reviewer
- Authority category: Product Module
- Capability level:
read-only(exactly one ofread-only | artifact-writing | execution-capable) - Product layer: cross-cutting (the functional axis -- see docs/roadmap/roadmap.md; orthogonal to category; this module guards promotions at every stage and enters none)
- Roadmap feature: F025 On-disk spec:
specs/019-pr-readiness-reviewer - Owner: the repo maintainer / PR reviewer (a named human)
- Status: Authored
What it does (one line)
Reads one PR's observed state and the committed readiness evidence it touches, and RENDERS a structured
merge_readyverdict -- a reading of evidence, never an authority.
Core Authority it READS
It reads; it never writes these. Inputs, unchanged.
mappings/<table>/readiness-status.yaml--current_stage, per-stagestatus,approvals[](named owner + date),blocking_reasons[].source-map.yaml-- approval / mapping-gate CLEARED metadata (when the PR touches a mapping).- The PR's declared test plan, the recorded
seshat check/retail validateand CI results, and the PR diff / file list (for the raw-data / secret / path scan).
Derived evidence it WRITES
- none (
read-only; the verdict is rendered EPHEMERALLY to the operator -- "presents / summarizes Core Authority", NOT "writes derived evidence". No tracked verdict file is written and no committed evidence artifact is created).
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.
- 11d ago First seen · 278 lines · 244 tokens per session scan A f85c23d520a5
pr-readiness-reviewer is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 244 tokens to every session and 4,327 once invoked, about $0.0012 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-31.
Other skills, from other repositories
pr-verify
Verify a Docglow change actually works before submitting or merging a PR. Runs the conformance suite, then a behavioral verification pass (flag matrix, artifact-join spot checks, pipeline contract sweep, payload budget). Use when reviewing a PR, self-reviewing a branch before opening a PR, or when asked to "verify…
audit-my-assumptions
Use when a finished thing — a source, a result, code, or the record — is about to be trusted or consumed; the gate fires before the work leans on it. Fire FIRST - before a number is BUILT on inherited sources or PRESENTED from them - when the silent assumptions baked into procs, queries, exports, or workbooks have not…
lookml_view_reviewer
Skill "lookml_view_reviewer" from G-Schumacher44/strata-oss, covering skill: lookmlviewreviewer, trigger, inputs, allowed tools and forbidden.
sql-reviewer
Review SQL queries and dbt models for best practices, performance, and anti-patterns.
test-review
You are an expert DataHub test reviewer. Your role is to evaluate pytest smoke tests against established testing standards, identify issues, and provide actionable feedback.
ktx-analytics
Use when answering a question that needs data from a ktx-connected database - investigating, analyzing, "how many", "show me", "what's the breakdown of", finding records by value, exploring tables, comparing periods, explaining metrics, or any data-analysis request. Triggers even when the user does not say…