Borrowing it
Nothing to install: this file belongs to Lab2A/metalworks. 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/Lab2A/metalworks/main/.claude/skills/pr-ready/SKILL.mdgit clone --depth 1 https://github.com/Lab2A/metalworksWrote 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/lab2a/metalworks/pr-ready)<a href="https://agentmods.dev/skills/lab2a/metalworks/pr-ready"><img src="https://agentmods.dev/badge/skills/lab2a/metalworks/pr-ready/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/lab2a/metalworks/pr-ready"><img src="https://agentmods.dev/badge/skills/lab2a/metalworks/pr-ready.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.00134 | $0.01077 |
| Opus 5.5 | $0.00054 | $0.00431 |
| Sonnet 5.5 | $0.00027 | $0.00215 |
| Haiku 4.5 | $0.00013 | $0.00108 |
Grade A, and why
pr-ready 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 2mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr-ready — pre-PR readiness check
You are checking whether the current branch is ready to open a PR against metalworks. Run the
automatable gates, inspect the diff for what CI can't check, and report a clean ✓ / ✗ / ? checklist
with what's left. metalworks is contract-first with four-surface parity (see docs/architecture.md) —
that's what most of these checks protect, so name the principle when something's off.
First, see what changed:
git fetch origin main -q
git diff --stat origin/main...HEAD # committed changes; add `git status -s` for uncommitted
1. The gate — run each, report pass/fail with the failing output
uv run ruff check .
uv run ruff format --check .
uv run pyright
uv run pytest -q
These are exactly what CI runs (matrix py3.11–3.13 × bare/all; you're running one interpreter, which is enough to catch real failures). A failure here blocks the PR — show the output and the fix.
2. Contract drift — the gate CI does NOT run
uv run python scripts/gen_ts_types.py --check
If it reports drift, the committed ts/contract.ts or src/metalworks/contract/schema/*.json are
stale. Run uv run python scripts/gen_ts_types.py and tell the contributor to commit the regenerated
files. This is the one gate CI misses, so it's the most common silent break.
3. Surface parity — inspect the diff (judgment, not a command)
If the diff adds or changes a primitive (a research verb / a user-facing capability), confirm it moved on all four surfaces and flag any missing one:
- Facade — a method on
Metalworksinsrc/metalworks/client.py. - CLI — a
@research_app.command(...)insrc/metalworks/cli/__init__.py(+ a_print_*renderer). - MCP — a body in
src/metalworks/mcp/tools.py, an async wrapper insrc/metalworks/mcp/server.py, and an entry in that file's_TOOL_WRAPPERStuple (forgetting the tuple = the tool isn't registered). - Skill — a
plugin/skills/<name>/SKILL.md.
A new contract model also means: it's in scripts/gen_ts_types.py MODELS (+ _SCHEMAS if a
snapshot root) and exported from src/metalworks/contract/__init__.py + __all__. Removing a surface
is the same rule in reverse — all four gone, plus every doc reference.
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.
- 2mo ago First seen · 88 lines · 134 tokens per session scan A d793cc2f6cd0
pr-ready is a skill published in the GitHub repository Lab2A/metalworks (7 stars, last pushed 4mo ago), licensed MIT. It adds 134 tokens to every session and 1,077 once invoked, about $0.0005 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
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.