verify-open-pstack SKILL.md skillA
verify-open-pstack from arjitj2/open-pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arjitj2/open-pstack/verify-open-pstack@git:20260925.ca39504Pins git:20260925.ca39504 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arjitj2/open-pstack
- Path
.agents/skills/verify-open-pstack/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260925.ca39504, committed Sep 25, 2026
- Size
- 7,426 bytes
- Repository stars
- 14
- License
- MIT
Verify Open Pstack through installed Codex and Claude Code skills and its shipped Bun CLIs. Use for real behavior proof, routing or setup changes, orchestration bookkeeping, and release evidence.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Verify Open Pstack
Read [the feature map](features/README.md) first. The primary product is the installed Pstack workflow in Codex and Claude Code. The secondary surfaces are the shipped CLI tools. A CLI proof establishes only that CLI's behavior, never installed skill discovery, parent decisions, or model execution.
This is repository maintenance tooling, outside `plugins/pstack`. Track work in GitHub Issues; this skill originated in [issue 26](https://github.com/arjitj2/open-pstack/issues/26). Read `UPSTREAM.md` before modifying upstream-derived content.
## Launch
Run from the Open Pstack checkout in one Bash session. There is no server, port, database seed, or build step. Bun installs the CLI dependencies; Python 3 checks observed JSON. Installation may access the package registry. Each CLI invocation exits on its own.
```bash
set -euo pipefail
VERIFY_REPO=$(git rev-parse --show-toplevel)
VERIFY_TOOLS="$VERIFY_REPO/plugins/pstack/skills/poteto-mode/scripts"
VERIFY_EVIDENCE=$(mktemp -d "$HOME/open-pstack-verification.XXXXXX")
VERIFY_SCRATCH=$(mktemp -d "${TMPDIR:-/tmp}/open-pstack-verify.XXXXXX")
export VERIFY_REPO VERIFY_TOOLS VERIFY_EVIDENCE VERIFY_SCRATCH
cleanup() {
…Read the whole file at its exact version.
How to install
mdr add arjitj2/open-pstack/verify-open-pstack@sha256:2d3b6f765278ded3The line at the top of this page pins the label git:20260925.ca39504, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fwk6tk36yvu4ilom)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 25, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7426 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
arjitj2/open-pstack · 14 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fwk6tk36yvu4ilom GET https://markdownregistry.com/api/v1/resolve?ref=arjitj2/open-pstack/verify-open-pstack GET https://markdownregistry.com/api/v1/blob/2d3b6f765278ded31667175ce0397758fea5bc6c5807f79e8e3b29166d913728
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.