rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Guardrails for AI coding agents: scope guard and locked behaviours for Claude Code, Cursor, Codex
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 25/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 37/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 124 (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Stet. Follow https://mcp.popnx.com/i/shamazkhan-stet.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 15, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Stet for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "stet": { "command": "npx", "args": [ "-y", "stet-cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"stet": {
"command": "npx",
"args": [
"-y",
"stet-cli",
"mcp"
]
}
}
}Use Stet and tell me what you can do for me, then show me one thing✓ If Claude says it is using Stet or shows a Stet tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Stet yet
Stet runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Stet
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Stet for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user stet -- npx -y stet-cli mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user stet -- npx -y stet-cli mcpYou should see Stet listed as connected
Use Stet and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Stet or shows a Stet tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Stet for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "stet": { "command": "npx", "args": [ "-y", "stet-cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Stet and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Stet or shows a Stet tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Stet for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "stet": { "type": "stdio", "command": "npx", "args": [ "-y", "stet-cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Stet and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Stet or shows a Stet tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user stet -- npx -y stet-cli mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"stet": {
"command": "npx",
"args": [
"-y",
"stet-cli",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"stet": {
"command": "npx",
"args": [
"-y",
"stet-cli",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"stet": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"stet-cli",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: stet-cliBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account shamazkhan, which owns the repo
Code last changed today
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/shamazkhan-stet)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed today, and the latest version (0.6.5) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Stet | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Stop AI coding agents from breaking what already works. · Website and docs: getstet.dev · Guides
Stet is a free, open-source CLI and MCP server for teams using Claude Code, Cursor, Codex, GitHub Copilot, Windsurf, Gemini CLI, ChatGPT or Claude. You set the scope of each AI task, lock the behaviours that must keep working, and Stet blocks any change that goes outside the task or breaks a lock. It works the same with every tool, and the agent can read the rules but can't rewrite them.
npx stet-cli init # in any git repo; Node 18+
Use it when your AI agent "tidies" files outside the task, breaks a feature you thought was safe, quietly edits a failing test, ignores your AGENTS.md / CLAUDE.md / Cursor rules, or forgets the project between chats.
.stet/charter.md. Stet keeps AGENTS.md (read by Codex, Cursor, Copilot and others) and CLAUDE.md in sync.stet check runs them all. If one fails, the AI fixes its change, not the test.stet check fails with a diff; stet lock approve accepts an intended change and logs why. No test file needed.stet guard flags every file changed outside scope or in protected paths, even if the agent already committed it.stet context builds a context pack from the live repo (charter, scope, locks, decisions, commits, uncommitted changes, file tree and the files you choose). Paste it into any chat instead of uploading your src folder.stet decide records "we chose X because Y", so the next session doesn't reopen it.stet scope set LIN-142 --allow "…" pulls the ticket's title and description from Linear into the context pack, so your AI gets the ticket and the code in one paste.LIN-142 Add CSV export) and stet pr writes the commit message and PR description from the real diff, scope, check results and decisions. The git hook adds the ticket ID to every commit.stet study "checkout" maps how a part of the code works: key files, the files they depend on, entry points (routes), an import-flow diagram, the tests that cover it and what protects it. It writes docs/flows/checkout.md, keeps your own notes on refresh, and tells you when the code has changed since.stet handoff writes an onboarding document for a new developer or CTO, built from the repo.stet mcp exposes all of this as tools to Claude Code, Cursor and any MCP client.No account. No telemetry. Your code never leaves your machine. Zero dependencies. Node 18+. Network calls are limited to two: once a day, when you run Stet in a terminal, it asks npm for the latest version number so it can offer an update (no code or repo information is sent; off in CI, or with STET_NO_UPDATE_CHECK=1). And if you set LINEAR_API_KEY, stet ticket fetches the Linear ticket you name (only the ticket ID is sent).
npm install -g stet-cli # or run any command with: npx stet-cli <command>
cd your-project stet init
stet init detects your stack and test command, then creates:
.stet/
charter.md what this is, stack, always / never rules ← edit this config.json name, protected paths, ignore globs locks.json locked behaviours scope.json current task scope decisions.md decision log AGENTS.md generated working agreement (your own text outside the stet block is kept) CLAUDE.md imports AGENTS.md for Claude Code
Commit .stet/, AGENTS.md and CLAUDE.md. Every agent and teammate then works from the same rules.
# once: lock what already works
stet lock add "Login works" --cmd "node --test test/auth.test.js" --protect "src/auth/**"
stet scope set "LIN-142 Add CSV export" --allow "src/export/**,test/export*" stet context --files "src/export/**" # copied to clipboard; paste into your chat
stet guard # anything outside scope or in protected paths? stet check # do all locked behaviours still pass?
stet pr # commit message + PR description (PR copied to clipboard) git commit -F .stet/.cache/commit.txt # "LIN-142: Add CSV export" + file list
Example output:
$ stet guard
Guarding 4 changed files (changes since 12b672b) · task: Add CSV export ✗ migrations/002_export.sql out of scope protected ✓ src/export/csv.js ✗ src/auth/session.js out of scope affects L2 ✓ test/export.test.js
✗ 2 files outside scope or protected. Revert, or widen the scope on purpose. ! Changes touch locked behaviour L2. Run: stet check --only L2
$ stet check Checking 2 locked behaviours ✗ L2 Login works (0.1s) │ not ok 1 - session expires after 30 minutes │ expected: 1800 │ actual: 0
✗ 1 locked behaviour broken: L2. Fix the change, not the check.
Many regressions are behaviour changes nobody wrote a test for: an export's column order, a renamed route, a mapping that shifted. Snapshot locks catch them with a tiny script that prints the behaviour:
stet lock add "Export format is stable" --snapshot "node scripts/export-sample.js" --protect "src/exports/**"
stet lock add "API routes unchanged" --snapshot "node scripts/print-routes.js" stet lock add "Report totals" --snapshot "python scripts/report.py" --mask "\d{4}-\d\d-\d\dT[\d:.]+Z"
Stet saves the output to .stet/snapshots/ as the approved version (commit it). From then on:
$ stet check
✗ L3 Export format is stable (0.2s, snapshot) │ output differs from the approved snapshot (- approved, + now): │ @@ line 1 @@ │ - id,name,email │ + id,email,name │ intended? approve it: stet lock approve L3 --why " "
stet lock approve L3 --why "PRO-91: email column first" saves the new output and logs a decision.--mask " "; matches become .stet guard flags any snapshot file edited by hand instead of through stet lock approve, and AGENTS.md tells agents never to approve snapshots themselves.| Command | What it does | ||
|---|---|---|---|
stet init [--name X] [--mcp] | Set up .stet/, AGENTS.md and CLAUDE.md. --mcp also writes .mcp.json. Safe to re-run. | ||
stet sync | Regenerate the Stet block in AGENTS.md (other commands do this automatically). | ||
stet scope set " " --allow " " [--ticket LIN-142] | Agree the task and the files it may touch. Records the current commit as the base. A ticket ID at the start of the task is picked up automatically. | ||
stet scope set … --strict | Refuse to start a scope while there are uncommitted files. Without it, earlier uncommitted work is *carried*: guard ignores it unless it changes again. | ||
stet scope carry / --all | Mark files guard flagged as leftovers from before the scope. | ||
stet scope done [--commit] [--force] | Run guard and check, commit only the task's files (with the stet pr message) and close the scope. | ||
| `stet scope [show\ | clear\ | ticket]` | Show or clear the scope, or print just the ticket ID. |
stet guard [--staged] [--base ref] [--warn] | Check changes since the scope base (committed, staged, unstaged and untracked). Exits 1 on violations unless --warn. | ||
stet lock add " " --cmd " " [--protect " "] | Lock a behaviour. --protect tells guard which files affect it. A command that is already locked is refused (--force to add anyway). | ||
stet lock rename L1 " " | Rename a lock, e.g. the test-suite lock stet init creates. | ||
stet lock add " " --snapshot " " [--mask " "] | Lock a command's output as an approved snapshot in .stet/snapshots/. | ||
stet lock approve L3 --why " " | Accept a changed snapshot on purpose; logged as a decision. | ||
| `stet lock [list\ | rm L2]` | List locks with their last result, or remove one. | |
stet check [--only L1,L2] | Run locked behaviours. Exits 1 if any fail and shows the failing lines. | ||
| `stet context [--files " "] [--changed] [--diff] [--copy\ | --stdout\ | --out f]` | Build the context pack. By default it writes .stet/context.md and copies it to the clipboard. |
stet decide " " [--why " "] | Add to the decision log. | ||
stet decisions [--all] | List decisions. | ||
stet ticket [LIN-142] [--stdout] [--cached] | Fetch a Linear ticket (needs LINEAR_API_KEY). It is included in stet context and linked in stet pr. With no ID, shows the current scope's ticket. | ||
stet pr [--base main] [--check] [--stdout] | Write .stet/.cache/commit.txt and .stet/.cache/pr.md from the diff since the scope was set: ticket, changed files, scope result, stet check results and decisions logged during the task. --check runs the locks first. | ||
stet study " " [--out file] [--max 12] | Map a flow: key and supporting files, routes, Mermaid diagram, tests, protection gaps. Writes docs/flows/ .md. | ||
stet study | List studied flows and which are out of date. | ||
stet context --flow | Context pack with the flow doc and all its files. | ||
stet handoff [--out HANDOFF.md] [--stdout] | Generate the onboarding pack. | ||
stet hook install [--check] | Add git hooks: pre-commit blocks commits that stage out-of-scope or protected files (--check also runs stet check); prepare-commit-msg adds the ticket ID to commit messages. | ||
stet update [--yes] | Check for a newer release and install it (asks first unless --yes). | ||
stet badge [--add] | Print the "guarded by stet" README badge, or add it to your README. | ||
stet status | One-screen summary. | ||
stet mcp / stet mcp install | Run the MCP server over stdio, or write .mcp.json. |
Add --json to any command for machine-readable output.
Took over a codebase, or about to change a part you don't know well?
stet study "checkout"
Writes docs/flows/checkout.md from the code itself:
path())stet lock commands for the gapsThen get the explanation from your AI:
stet context --flow checkout # the flow doc + all its files, copied to your clipboard
The doc includes a ready prompt. Paste the answer into its How it works section: Stet keeps that section and your Notes when you refresh the doc. stet study on its own lists your flows and flags the ones whose code changed since they were written; stet status