Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/usefulsoftwareco/executor/stacknpx skills add UsefulSoftwareCo/executor --skill stackgit clone --depth 1 https://github.com/UsefulSoftwareCo/executorWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00061 | $0.02114 |
| Opus 5 | $0.00030 | $0.01057 |
| Sonnet 5 | $0.00012 | $0.00423 |
| Haiku 4.5 | $0.00006 | $0.00211 |
Grade A, and why
stack scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- stack — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack
Use the local stack CLI for squash-safe stacked PR repair. It is designed for
repos where PRs are squash-merged and merged branches are deleted, so Git ancestry
alone cannot preserve stack intent.
Keep ordinary editing and commits on plain git. Use stack only for stack
intent, stack inspection, sync, merge, and undo workflows.
Mental Model
dev
└─ stack-a #101
└─ stack-b #102
└─ stack-c #103
Stack intent is persisted in .git/stack/state.json as stack links:
- branch
- parent branch
- merge-base anchor
- PR number
Mutating sync and merge workflows write .git/stack/undo.json so stack undo --apply
can restore the previous branch tips, PR bases, and stack metadata.
Common Commands
stack status: show the relevant tracked stack graph and include open PR details when GitHub is available.stack guide: print the opinionated happy path for agents and humans.stack track <branch> --onto <parent>: record stack intent for an existing branch.stack sync --dry-run [branch]: preview inferred PR-base stack links and repairs without changing branches or PRs.stack sync [branch]: infer clear PR-base stack links, repair descendants, retarget PRs, and refresh stack blocks. With a branch argument, sync only the stack containing that branch.stack sync --continue-on-failure/stack sync --keep-going: process independent stacks, summarize successes and failures, and exit nonzero if any stack failed.stack doctor: inspect local Git, GitHub, stack metadata, trunk branches, and undo journal health without changing anything.stack merge [branch]: dry-run root PR merge plus descendant repair.stack merge [branch] --apply: retarget immediate child PRs, squash-merge the root PR, then repair descendants.stack merge [branch] --auto: retarget immediate child PRs, enable GitHub auto-merge, wait, then repair descendants.stack merge --auto --through <branch-or-pr>: repeat auto-merge one root at a time until the target branch or PR lands.stack history: show the most recent applied repair journal.stack undo: dry-run restore of the most recent applied repair.stack undo --apply: restore branches, PR bases, and stack metadata from the journal.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 222 lines · 61 tokens per session scan A 6c567927a8fe
stack is a skill published in the GitHub repository UsefulSoftwareCo/executor (3,466 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 2,114 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…