Skip to content
Back to search

pstack-codex

Codex-native port of Lauren Tan's pstack: 47 skills, 23 playbooks, agent personas, multi-agent workflows, and Benny automation adapters. Includes a Codex marketplace and installer.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/scriptedalchemy--pstack-codex/badge.svg)](/listings/scriptedalchemy--pstack-codex)

HTML

<a href="/listings/scriptedalchemy--pstack-codex"><img src="/api/listings/scriptedalchemy--pstack-codex/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Requires a Codex build with `codex plugin` support, Git, and Python 3.11+ for validation.

If your shell defaults to an older Python, set `PSTACK_PYTHON` to the Python 3.11+ executable when running the installer (for example, `PSTACK_PYTHON=/opt/homebrew/bin/python3.13 ./scripts/install.sh` on a matching Homebrew installation).

git clone https://github.com/ScriptedAlchemy/pstack-codex.git
cd pstack-codex
./scripts/install.sh

The script validates the package, registers this checkout as the `pstack-codex` marketplace, and installs `pstack@pstack-codex`. It does not edit your Codex configuration by hand or overwrite personal agent definitions. Start a new Codex task after installation and invoke `$setup-pstack`. Most pstack skills are intentionally explicit-only; invoke them with `$<skill-name>`, such as `$interrogate`. Ask to use `$poteto-mode` as a standing instruction for the current task when you want the orchestration workflow. Repository-local skills belong under `.agents/skills`, not `.codex/skills`.

Use `$automate-maintainer sokra, alex for owner/repo` to draft conventions from named GitHub users. Use `$automate-team owner/repo` to discover active core contributors and mine their code, reviews, and design discussions into a team mode. Both workflows keep evidence and ownership explicit; they create skills without posting or acting as the people studied.

Alternatively, install the published marketplace without cloning:

codex plugin marketplace add ScriptedAlchemy/pstack-codex
codex plugin add pstack@pstack-codex

Optional named custom agents are provided in `plugins/pstack/codex-agents`. Review these before copying them into `~/.codex/agents`; the workflows also support generic workers loaded with the corresponding persona instructions, so copying agents is not required. Run `setup-pstack` to configure model preferences and connected integrations. Hooks, MCPs, and external automation services are not automatically invented or enabled: consult the runtime contract and workflow setup instructions for the actual supported equivalents.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 81 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # pstack for Codex
  2. A Codex-native adaptation of [Lauren Tan's pstack](https://github.com/cursor/plugins/tree/main/pstack), preserving its workflows, playbooks, principles, and agent personas while adapting host-specific execution to Codex. This is an independent port, not an official Cursor or OpenAI plugin.
  3. The plugin lives in `plugins/pstack`; `.agents/plugins/marketplace.json` makes this repository a native Codex marketplace. Read the [runtime contract](plugins/pstack/CODEX.md), [port coverage and runtime boundaries](PARITY.md), and [per-file source coverage](FILE-COVERAGE.md). Tool availability depends on the Codex host, permissions, and connected integrations. No credentials are bundled.
  4. ## Install
  5. Requires a Codex build with `codex plugin` support, Git, and Python 3.11+ for validation.
  6. If your shell defaults to an older Python, set `PSTACK_PYTHON` to the Python 3.11+
  7. executable when running the installer (for example,
  8. `PSTACK_PYTHON=/opt/homebrew/bin/python3.13 ./scripts/install.sh` on a matching
  9. Homebrew installation).
  10. ```sh
  11. git clone https://github.com/ScriptedAlchemy/pstack-codex.git
  12. cd pstack-codex
  13. ./scripts/install.sh
  14. ```
  15. The script validates the package, registers this checkout as the `pstack-codex` marketplace, and installs `pstack@pstack-codex`. It does not edit your Codex configuration by hand or overwrite personal agent definitions. Start a new Codex task after installation and invoke `$setup-pstack`. Most pstack skills are intentionally explicit-only; invoke them with `$<skill-name>`, such as `$interrogate`. Ask to use `$poteto-mode` as a standing instruction for the current task when you want the orchestration workflow. Repository-local skills belong under `.agents/skills`, not `.codex/skills`.
  16. Use `$automate-maintainer sokra, alex for owner/repo` to draft conventions from named GitHub users. Use `$automate-team owner/repo` to discover active core contributors and mine their code, reviews, and design discussions into a team mode. Both workflows keep evidence and ownership explicit; they create skills without posting or acting as the people studied.
  17. Alternatively, install the published marketplace without cloning:
  18. ```sh
  19. codex plugin marketplace add ScriptedAlchemy/pstack-codex
  20. codex plugin add pstack@pstack-codex
  21. ```
  22. Optional named custom agents are provided in `plugins/pstack/codex-agents`. Review these before copying them into `~/.codex/agents`; the workflows also support generic workers loaded with the corresponding persona instructions, so copying agents is not required. Run `setup-pstack` to configure model preferences and connected integrations. Hooks, MCPs, and external automation services are not automatically invented or enabled: consult the runtime contract and workflow setup instructions for the actual supported equivalents.
  23. ## Verify and develop
  24. ```sh
  25. ./scripts/validate.sh
  26. ```
  27. The documentation checker in `scripts/test.sh` also checks skill names, relative links, anchors, and model defaults against the shipped tree.
  28. The portable validator checks the marketplace, manifest, all skill entry points, invocation policies, relative runtime links, agent TOML, and every file in the pinned upstream inventory. Run `python3 scripts/parity.py --report` for a per-file retained/adapted/replaced report. Runtime-dependent integrations still need an authenticated end-to-end test in the target host; structural checks do not prove external-service delivery.
  29. The [integration test report](INTEGRATION-TESTS.md) separates live host/service
  30. proof from fixture coverage. Run `bash scripts/test.sh` for the combined suite
  31. after installing the Bun helper dependencies below. The bot UI ships a tested
  32. loopback HTTP-to-Codex bridge, and Benny ships a tested durable polling ledger;
  33. neither starts automatically on installation.
  34. Helper-script tests require Bun and Node 22.15 or later. The statechart suite also exercises TLC/Java and Pele PNG rendering when their dependencies are available; unavailable optional dependencies are reported as skipped tests. Run `node plugins/pstack/skills/statechart/scripts/statechart.mjs --help` for setup, including `TLA2TOOLS` and `JAVA` overrides. Rendering downloads pinned npm packages into the user cache, outside the plugin.
  35. Install the Bun test dependencies:
  36. ```sh
  37. cd plugins/pstack/skills/poteto-mode/scripts
  38. bun install --frozen-lockfile
  39. bun test orch watch-pr check-plan.test.ts
  40. bun run typecheck
  41. node --test check-plan.test.mjs worktree-audit.test.mjs
  42. ```
  43. Before reinstalling a modified local plugin, use Codex's `plugin-creator` skill cachebuster/reinstall flow; then run `./scripts/install.sh` and start a new task. Keep the published version updated when shipping changes so existing installations do not reuse stale caches.
  44. Move test-only `node_modules` outside the plugin directory before installation;
  45. the installer refuses to package it. Remove temporary test dependencies after validation; do not commit or distribute them.
  46. ## Track upstream safely
  47. The source snapshot is pinned in [UPSTREAM.json](UPSTREAM.json). This repository uses its own native layout and history; **do not merge the entire Cursor plugins monorepo into this repository**.
  48. ```sh
  49. git remote add upstream https://github.com/cursor/plugins.git # once, if absent
  50. ./scripts/check-upstream.sh
  51. ```
  52. The audit fetches upstream Git objects and prints pstack-only changes since the pinned source. It never replaces translated files or advances the pin. See [UPDATING.md](UPDATING.md) for the review-and-port procedure. `origin` is this port; `upstream` remains the original repository.
  53. ## License and attribution
  54. MIT. Original pstack copyright © 2026 Lauren Tan; original license is retained in [LICENSE](LICENSE) and the plugin. Codex adaptation changes are distributed under the same license. Upstream version: 0.15.36, source commit `236e5481d05cbadc315b374a5de54971858c27bb`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.