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/wrdn-effect-promise-exitnpx skills add UsefulSoftwareCo/executor --skill wrdn-effect-promise-exitgit 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/wrdn-effect-promise-exit)<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/wrdn-effect-promise-exit"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/wrdn-effect-promise-exit.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00063 | $0.01155 |
| Opus 5 | $0.00032 | $0.00577 |
| Sonnet 5 | $0.00013 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
wrdn-effect-promise-exit 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 4d 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:
- wrdn-effect-promise-exit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You fix one pattern: a React handler awaits an effect-atom mutation in mode: "promise" and catches failures with try/catch.
The preferred UI boundary is mode: "promiseExit" plus Exit.isFailure. This keeps mutation failures as values, matches Effect's error model, and prevents optimistic mutation cleanup from depending on thrown exceptions.
Trace before changing
- Find the mutation setter. Look for
const doX = useAtomSet(<mutationAtom>, { mode: "promise" }). - Confirm it is an effect-atom mutation boundary. The setter should come from
@effect/atom-reactand a mutation atom from./atoms,../api/atoms, or plugin React atoms. - Find thrown-control handling. The same handler has
try { await doX(...) } catch (e) { ... }, usually setting error text, resettingadding/saving, or showing a toast. - Check for non-mutation async work in the same block. If the block also awaits follow-up mutations, convert those to
promiseExittoo or keep a narrow boundary only around truly non-effect APIs. - Do not rewrite unrelated local async code. Probe requests, OAuth popup helpers,
fetch, and browser APIs may need a different skill unless the lint finding specifically points at the mutation call.
Fix shape
- Change the setter to
{ mode: "promiseExit" }. - Import
* as Exit from "effect/Exit"if missing. - Import
* as Option from "effect/Option"only when extracting an optional error. - Replace
try/catcharound the mutation with:const exit = await doX(args);if (Exit.isFailure(exit)) { ...; return; }- success work after the failure branch.
- Use
Exit.findErrorOption(exit)when preserving an existing error message or typed error branch. - Keep existing typed error handling when present, e.g.
SecretInUseError,ConnectionInUseError.
Bad
const doAdd = useAtomSet(addGraphqlSource, { mode: "promise" });
const handleAdd = async () => {
setAdding(true);
setAddError(null);
try {
await doAdd({
params: { scopeId },
payload,
reactivityKeys: sourceWriteKeys,
});
props.onComplete();
} catch (e) {
setAddError(e instanceof Error ? e.message : "Failed to add source");
setAdding(false);
}
};
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.
- 4d ago First seen · 116 lines · 63 tokens per session scan A 906ed2800e3b
wrdn-effect-promise-exit is a skill published in the GitHub repository UsefulSoftwareCo/executor (3,494 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,155 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
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
flags
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.