pstack-claude: rigorous agent workflows, ported

TL;DR: pstack-claude is a small MIT licensed JavaScript repository, 1,154 stars and 129 forks, whose job is porting. It carries Poteto’s pstack agent workflows from Cursor primitives to six other harnesses, including Claude Code, Codex, Pi, OpenCode and Gemini.

What the project actually is

Most trending agent repositories sell you a new assistant. This one sells you a translation layer, which is a rarer and more useful thing to see trend.

The description reads: Claude Code, Codex, Pi, OpenCode, Gemini, and Prime Agent versions of Poteto’s pstack, with rigorous agent workflows and Cursor primitives translated for other harnesses. The word translated is doing real work there. The implicit claim is that a workflow system originally built for Cursor should be usable in the assistants most people actually run, and that pstack-claude is the port.

Field	Value
Full name	michael-denyer/pstack-claude
Description	Claude Code, Codex, Pi, OpenCode, Gemini, and Prime Agent versions of Poteto’s pstack. Rigorous agent workflows with Cursor primitives translated for other harnesses.
Stars	1,154
Forks	129
Primary language	JavaScript
License	MIT
Topics	agent-plugin, agent-skills, agentic-ai, anthropic, chatgpt
Homepage	none listed
Created	2026-05-26
Last push	2026-10-04
Owner type	User

Two of the topics, anthropic and chatgpt, name the vendors directly, and agent-plugin alongside agent-skills suggests the package installs as a plugin or skill bundle rather than a library you import. The repository has no homepage set, so the README and the wiki are the documentation.

Why a port is worth its own repository

Agent workflows are not portable by default. The primitives that make a workflow work, the way a tool is declared, the shape of a subagent definition, the assumptions about context and file layout, are all harness-specific in practice. A workflow that leans on Cursor’s primitives does not run in Claude Code without work, and that work is repetitive across every workflow you want to move.

Centralising it in one repository turns a per-workflow porting problem into a single maintenance surface. The 1,154 stars against 129 forks is a narrower ratio than the video and CAD projects in today’s batch, and that tracks with the nature of the thing. You install a plugin and use it, or you fork it and adapt it, rather than reading through the source to learn from it.

The rigorous in the description is a claim about the workflows themselves, and it is the one part you cannot check from metadata. Rigour in agent workflows is a matter of opinion about what a workflow ought to enforce.

How to look at it yourself

This is a JavaScript repository, so the usual read is enough to judge it:

git clone https://github.com/michael-denyer/pstack-claude.git
cd pstack-claude
ls

The topic list confirms the harness coverage claimed in the description, and it is a cheap check before you try to install anything:

curl -s https://api.github.com/repos/michael-denyer/pstack-claude \
  | jq '{topics, language, license: .license.spdx_id, stars: .stargazers_count}'

When to use it

The fit is narrow and clear. If you use Cursor workflows and have hit a wall running them elsewhere, or you want one disciplined workflow set to try in more than one assistant, this is the thing to look at. The MIT license removes any friction from adapting it to your own process.

If you are still choosing a harness, this is the wrong repo to start with. It assumes you already know pstack and want it somewhere specific. A wiki is enabled, so per-harness install notes are likely there, which is where you would confirm the actual package name and setup for whichever assistant you run.

Source and Accuracy Notes

• Source repository: github.com/michael-denyer/pstack-claude (verified via GitHub API html_url)
• License: MIT (verified via GitHub API license.spdx_id)
• Stars at time of writing: 1,154
• Forks at time of writing: 129
• Facts in this post come from the GitHub API repository endpoint and the repository description only. The README was not fetched, so workflow names, install commands and package names are not claimed here beyond what the description, topics, language and license fields state.