Executor is a shared integration layer that lets AI agents use tools from MCP servers, OpenAPI specifications, GraphQL APIs, and custom JavaScript functions through one catalog. It centralizes credentials and per-tool access policies so MCP-compatible agents can reuse the same integrations.
Borrowing it
Nothing to install: this file belongs to UsefulSoftwareCo/executor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/UsefulSoftwareCo/executor/main/.agents/skills/stack/SKILL.mdgit clone --depth 1 https://github.com/UsefulSoftwareCo/executorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/usefulsoftwareco/executor/stack)<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/stack"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/stack/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/stack"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/stack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00061 | $0.02114 |
| Opus 5.5 | $0.00024 | $0.00846 |
| Sonnet 5.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 2mo ago.
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.
- 2mo ago First seen · 222 lines · 61 tokens per session scan A 6c567927a8fe
stack is a skill published in the GitHub repository UsefulSoftwareCo/executor (4,297 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 2,114 once invoked, about $0.0002 per session on Opus 5.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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.