What is verify-open-pstack?

A repository procedure for verifying an Open Pstack pull request at its exact candidate commit. It runs machine-checked assertions in Claude Code and Codex sessions, publishes evidence, and sets a live-gate status without merging the change.

Use it to run the repository's verification script, test a pull request or trusted main branch, and publish the result for the exact commit.

It prevents a review from testing a different commit than the one being judged and keeps untrusted candidate code separate from publishing credentials. It also records evidence that others can inspect.

How ericlitman/open-pstack configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to ericlitman/open-pstack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ericlitman/open-pstack/main/.claude/skills/verify-open-pstack/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ericlitman/open-pstack

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ericlitman/open-pstack/verify-open-pstack/github.svg)](https://agentmods.dev/skills/ericlitman/open-pstack/verify-open-pstack)

Your own site

<a href="https://agentmods.dev/skills/ericlitman/open-pstack/verify-open-pstack"><img src="https://agentmods.dev/badge/skills/ericlitman/open-pstack/verify-open-pstack/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ericlitman/open-pstack/verify-open-pstack"><img src="https://agentmods.dev/badge/skills/ericlitman/open-pstack/verify-open-pstack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,622 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00041	$0.02622
Opus 5.5	$0.00016	$0.01049
Sonnet 5.5	$0.00008	$0.00524
Haiku 4.5	$0.00004	$0.00262

Measured yesterday against content hash 2b5b582f495b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify-open-pstack 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 yesterday.

The scan reads SKILL.md. This mod also ships 23 executable files (features/recipes.ts, scripts/catalog.test.ts, scripts/cli.test.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/verify-open-pstack/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verify Open Pstack

Launch

This repository-local, non-shipped skill is shared with Codex through .agents/skills/verify-open-pstack. Verifier-changing PRs run from a checkout of their reviewed candidate head; all other PRs run from trusted main. The trusted parent owns GitHub reads and publication; candidate processes never receive publisher credentials. Its only GitHub writes are one structured evidence comment and live-gate status on the exact candidate SHA; it never queues or merges.

Install development dependencies separately when testing this skill; verify.sh does not install at runtime:

(cd .claude/skills/verify-open-pstack && bun install --frozen-lockfile --ignore-scripts)

Then run from the trusted publisher checkout:

PR=111 # supplied delivery PR number
SESSION="$(mktemp -d "${TMPDIR:-/tmp}/open-pstack-evidence.XXXXXX")"
EVIDENCE="$SESSION/live" # must not exist yet
.claude/skills/verify-open-pstack/scripts/verify.sh doctor --output "$SESSION/probe"
.claude/skills/verify-open-pstack/scripts/verify.sh run --pr "$PR" --feature claude:project-skill --self-test --output "$EVIDENCE"

Pick the features that exercise the PR's changed behavior and pass each as --feature <harness>:<feature>, repeatable. List the same features in the PR body, where review sees them. The run exercises only the named features, plus project-skill in both harnesses when classification reaches it or under --self-test. Before any install or GitHub write, verify.sh run makes three checks:

Scope: a runtime change needs at least one --feature, and every named feature must be in the PR's classified reach. The refusal names each refused feature and the reachable set. A manifest change that only bumps the version reaches only hook:startup in that manifest's harness.
Count: the run prints the number of headless sessions the named features and automatic project-skill checks will start.
Limit: above 12 sessions, the run refuses unless you pass --wide "<reason>". The reason must be printable ASCII, at most 160 characters, without backticks or angle brackets. The evidence comment records the planned count and the reason.

Read the full file on GitHub · 106 lines

Files

What ships with it

36 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.

Changes

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.

yesterday Changed · +4 lines 2b5b582f495b
4d ago Changed · +1 lines 8eeb3cbbfda3
6d ago Changed · +1 lines 1c54c0f875f6
12d ago Changed · +2 lines 67f00cd4bc84
13d ago First seen · 98 lines · 41 tokens per session scan A 2315256a70a3

Subscribe to this mod's changes

verify-open-pstack is a skill published in the GitHub repository ericlitman/open-pstack (427 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,622 once invoked, about $0.0002 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-05.

Commits Git and workflow Testing

github-copilot-upgrader

Use this to update the Github Copilot CLI/SDK.

microsoft/vscode · 18 tokens

workflow-patterns

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

wshobson/agents · 35 tokens

meta-pre-commit-quality-gate

Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.

opensquilla/opensquilla · 68 tokens

open-pstack: Skill for Claude Code