Skip to content
Back to search

pstack-for-codex

Codex-native engineering workflows derived from pstack, with 45 explicit skills and 23 Poteto Mode playbooks.

Safety scan

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

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Aqua-123/pstack-for-codex with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Aqua-123/pstack-for-codex'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

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

HTML

<a href="/listings/aqua-123--pstack-for-codex"><img src="/api/listings/aqua-123--pstack-for-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.

This public repository is a Codex marketplace. Install it directly from GitHub:

codex plugin marketplace add Aqua-123/pstack-for-codex
codex plugin add pstack-for-codex@pstack-for-codex-local

For a local checkout, replace `Aqua-123/pstack-for-codex` with its absolute path. Confirm the installed plugin:

codex plugin list --json

Codex CLI `0.153.4` does not expose an offline runtime skill-index command. The release suite validates the skill catalog from the installed artifact; start a new task to exercise prompt-time skill discovery.

All 48 skills require explicit invocation. Codex stores their full identities under the `pstack-for-codex` namespace. In a prompt, invoke a skill with its registered `$name`:

$poteto-mode add a --json flag to this command. Keep text output byte-identical. Verify both modes.

Start a new task after installation so Codex reloads the plugin catalog. See [Set up pstack](./docs/guide/01-setup.md) for the complete walkthrough.

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 · 148 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. `pstack-for-codex` is a Codex-native derivative of [pstack](https://github.com/cursor/plugins/tree/main/pstack). It packages deliberate engineering workflows as 59 explicit-only skills and 23 Poteto Mode playbooks.
  3. Use `$poteto-mode` for a substantial engineering task. It selects a playbook, records the work as verifiable steps, and invokes narrower skills when the steps need them. The parent task keeps authority for integration, external writes, commits, pushes, and the final result.
  4. ## Install
  5. This public repository is a Codex marketplace. Install it directly from GitHub:
  6. ```bash
  7. codex plugin marketplace add Aqua-123/pstack-for-codex
  8. codex plugin add pstack-for-codex@pstack-for-codex-local
  9. ```
  10. For a local checkout, replace `Aqua-123/pstack-for-codex` with its absolute path. Confirm the installed plugin:
  11. ```bash
  12. codex plugin list --json
  13. ```
  14. Codex CLI `0.153.4` does not expose an offline runtime skill-index command. The release suite validates the skill catalog from the installed artifact; start a new task to exercise prompt-time skill discovery.
  15. All 59 skills require explicit invocation. Codex stores their full identities under the `pstack-for-codex` namespace. In a prompt, invoke a skill with its registered `$name`:
  16. ```text
  17. $poteto-mode add a --json flag to this command. Keep text output byte-identical. Verify both modes.
  18. ```
  19. Start a new task after installation so Codex reloads the plugin catalog. See [Set up pstack](./docs/guide/01-setup.md) for the complete walkthrough.
  20. ## Optional agent profiles
  21. The skills work without custom agent profiles. Use `$setup-pstack` only when you want to install the two optional profiles:
  22. - `pstack-poteto-agent` for implementation and orchestration.
  23. - `pstack-comment-sicko` for read-only comment review.
  24. Setup writes either project profiles under `.codex/agents/` or user profiles under `~/.codex/agents/`. It records file hashes in a receipt and refuses to overwrite files owned by someone else. An explicit `model` and `reasoning_effort` pair is accepted only when a supported Codex model-list surface proves the pair. Otherwise the profile inherits the parent model and the receipt records that the requested pair is unverified.
  25. Read [Agent setup and model evidence](./docs/codex-adaptation.md#agent-setup-and-model-evidence) before changing profiles.
  26. ## Use the skills
  27. `$poteto-mode` is the main entry point:
  28. ```text
  29. $poteto-mode this retry path creates duplicate rows. Reproduce it first, fix the root cause, and verify the real behavior.
  30. ```
  31. The other skills are useful when you want one specific operation:
  32. | Skill | Use it for |
  33. |---|---|
  34. | [`$how`](./skills/how/SKILL.md) | Trace how a subsystem works. |
  35. | [`$why`](./skills/why/SKILL.md) | Answer why code reached its current shape from the record: the commits and PR discussion behind it, with inferences marked. |
  36. | [`$recall`](./skills/recall/SKILL.md) | Rebuild recent project context through supported task history and live state. |
  37. | [`$architect`](./skills/architect/SKILL.md) | Settle types, callers, and module boundaries before implementation. |
  38. | [`$arena`](./skills/arena/SKILL.md) | Compare isolated attempts at the same brief. |
  39. | [`$swarm`](./skills/swarm/SKILL.md) | Cover independent slices or races and aggregate the result. |
  40. | [`$interrogate`](./skills/interrogate/SKILL.md) | Send adversaries to break a diff and keep only findings a rerun proves, using different verified model profiles when available. |
  41. | [`$statechart`](./skills/statechart/SKILL.md) | Check a TLA+ model and draw it as a Mermaid statechart with the shortest path to each broken rule. |
  42. | [`$create-formal-verification-skill`](./skills/create-formal-verification-skill/SKILL.md) | Prove one property that tests cannot reach and generate a project-local skill that rechecks it. |
  43. | [`$maintain-formal-verification-skill`](./skills/maintain-formal-verification-skill/SKILL.md) | Update and rerun a formal verification skill after the covered code changes. |
  44. | [`$tdd`](./skills/tdd/SKILL.md) | Reproduce a bug with a failing test before fixing it. |
  45. | [`$no-comments`](./skills/no-comments/SKILL.md) | Review comments and remove ones that do not earn their place. |
  46. | [`$unslop`](./skills/unslop/SKILL.md) | Remove vague or machine-shaped prose. |
  47. | [`$ketchup`](./skills/ketchup/SKILL.md) | Catch up on what changed, with every waiting decision listed. |
  48. | [`$ketchup-video`](./skills/ketchup-video/SKILL.md) | Deliver the `$ketchup` catch-up as a short subtitled video when a video tool is available. |
  49. | [`$show-me-your-work`](./skills/show-me-your-work/SKILL.md) | Keep a reviewable `decisions.tsv` trail. |
  50. | [`$setup-benny`](./skills/setup-benny/SKILL.md) | Inspect or configure the dormant Benny polling pack. |
  51. | [`$make-bot-ui`](./skills/make-bot-ui/SKILL.md) | Build a local UI for an authenticated user-owned webhook. |
  52. Browse the [complete skill directory](./skills/) or read the [pstack guide](./docs/guide/README.md).
  53. `$poteto-help` is explicit-only. Invoke it when you need a skill route, a prompt structure, or a copyable prompt. It does not start the suggested work.
  54. ## Runtime boundaries
  55. Codex agents may share one filesystem. Read-only work can share a checkout. Parallel writers need exclusive file ownership, separate worktrees, or separate output directories. When safe isolation is unavailable, pstack runs the work serially.
  56. The active user request is the authority boundary. A child cannot add an external write, destination, credential, repository, or lifecycle object. Goals, heartbeats, scheduled tasks, monitors, and separate user-owned tasks are created only when the user requests that lifecycle or gives an equivalent terminal condition such as an overnight run.
  57. Hooks can keep Poteto Mode active across later turns only after Codex trusts the plugin hook source. Without trusted hook evidence, `$poteto-mode` still works for the current turn and reports `current-turn-only`. Say `disable $poteto-mode` to clear the session state.
  58. Optional connectors and control tools are detected at run time. A missing capability triggers the fallback declared by the skill. Work stops when that capability is required for correctness or credential isolation.
  59. ## Benny stays paused
  60. [Benny](./automations/benny/README.md) is an optional polling pack for issue triage and reproduction. Installation does not create or activate an automation. `$setup-benny` copies the pack into a target project only after explicit authority.
  61. The two stable automation names are `pstack-benny-triage` and `pstack-benny-reproduce`. Setup creates or updates them only when the user asks, and it leaves both `PAUSED`. Activation needs a separate request after all six canaries pass. Polling is not event delivery, so work can begin up to one schedule interval after a source change.
  62. ## Develop and verify
  63. The metadata and resource validator requires Node.js. The watch-PR scripts require [Bun](https://bun.sh/).
  64. ```bash
  65. node scripts/validate-plugin.mjs --json
  66. node --test tests/*.test.mjs
  67. cd skills/poteto-mode/scripts
  68. bun install --frozen-lockfile
  69. bun test --timeout 30000 check-plan.test.ts watch-pr
  70. bun run typecheck
  71. ```
  72. The `$statechart` scripts run on Node.js 22.18+ and have their own offline tests. Tests that need TLC skip themselves unless `TLA2TOOLS` points to `tla2tools.jar`:
  73. ```bash
  74. npm run test:statechart
  75. ```
  76. The validator reports Bun as an optional capability. Skills that depend on the Bun scripts must stop or declare their fallback when Bun is unavailable.
  77. ## Update or remove
  78. Refresh the configured Git marketplace, then reinstall from the refreshed snapshot:
  79. ```bash
  80. codex plugin marketplace upgrade pstack-for-codex-local
  81. codex plugin remove pstack-for-codex@pstack-for-codex-local
  82. codex plugin add pstack-for-codex@pstack-for-codex-local
  83. ```
  84. Remove the plugin and its marketplace registration with:
  85. ```bash
  86. codex plugin remove pstack-for-codex@pstack-for-codex-local
  87. codex plugin marketplace remove pstack-for-codex-local
  88. ```
  89. Plugin removal does not delete project or user files created by `$setup-pstack` or `$setup-benny`. Use those skills to inspect receipts and remove only unchanged, owned files. Benny configuration and mutable state survive uninstall unless the user separately authorizes a purge.
  90. ## Origin and maintenance
  91. This repository contains only the modified Codex version. It does not publish a raw upstream branch or snapshot commit, and the delivered checkout does not keep an upstream remote.
  92. [NOTICE](./NOTICE), [`upstream.lock.json`](./upstream.lock.json), and the [compatibility map](./compatibility/pstack-map.json) record the source commit, license, file hashes, and migration status. [UPSTREAM.md](./UPSTREAM.md) explains how maintainers refresh that evidence through a temporary local source checkout.
  93. See [Codex adaptation notes](./docs/codex-adaptation.md) for the behavioral changes and current limits.
  94. ## License
  95. MIT. See [LICENSE](./LICENSE) and [NOTICE](./NOTICE).
  96. The 0.5.0 refresh tracks upstream pstack 0.15.42. It adds `$statechart`, `$create-formal-verification-skill`, `$maintain-formal-verification-skill`, and `$ketchup-video`. Orchestrate becomes an agentic playbook and the orch scripts are removed. `$how`, `$why`, and `$interrogate` each collapse to one file, and `$interrogate` keeps only findings a rerun proves. Codex authority, explicit-only discovery, profile inheritance, and supported history access remain enforced.
  97. The 0.4.0 refresh tracks upstream pstack 0.15.24. It adds `$in-your-own-words`, `$ketchup`, and `$sharpen`, improves plan fence checks, and updates PR watching and forge-neutral stack handling. Codex authority, explicit-only discovery, profile inheritance, and supported history access remain enforced.

Ratings and comments

Sign in to rate this skill.

Sign in

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