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/wrdn-effect-atom-optimistic/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/wrdn-effect-atom-optimistic)<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/wrdn-effect-atom-optimistic"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/wrdn-effect-atom-optimistic/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/wrdn-effect-atom-optimistic"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/wrdn-effect-atom-optimistic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Prompt Injection · line 49 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00102 | $0.02628 |
| Opus 5.5 | $0.00041 | $0.01051 |
| Sonnet 5.5 | $0.00020 | $0.00526 |
| Haiku 4.5 | $0.00010 | $0.00263 |
Grade A, and why
wrdn-effect-atom-optimistic 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:
- wrdn-effect-atom-optimistic — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You audit React code in this repo for one thing: did the author roll their own optimistic-update layer on top of an effect-atom query atom instead of using Atom.optimistic / Atom.optimisticFn?
This is not a security skill. It is a correctness skill. The hand-rolled patterns have a known race condition: concurrent mutations on the same row stomp each other's done() calls and the UI flickers back to a stale server value. The fix is the effect-atom primitives, which track transitions and refresh authoritatively. The repo already migrated policies and codified the pattern at .skills/effect-atom-optimistic-updates/SKILL.md.
Trace. Do not pattern-match a useState and call it a day. The signal is "this state is tracking an in-flight mutation alongside an effect-atom query," not "this component uses local state."
Trace before reporting
- Find the mutation. Is the component calling
useAtomSet(<somethingMutation>)frompackages/react/src/api/atoms.tsx? If not, this skill does not apply. - Find the read. Is the same component or its parent reading the matching list via
useAtomValue(<sameThingAtom>(scopeId))? If yes, the optimistic substitute exists or should exist. - Find the bookkeeping. Look for any of these alongside the mutation call:
useState,useReducer,useRefholding "pending" / "placeholder" / "in-flight" / "optimistic" values keyed by row idAtom.makeof a list / map / set of pending entries, in the component or inpackages/react/src/api/optimistic.tsx- Calls into
usePendingResource,usePoliciesWithPending,usePendingPolicies,mergePending, or any helper named like that try { await doMutate(...) } finally { placeholder.done() }shapes- Manual id minting (
pending-${...},crypto.randomUUID) in the page-level handler rather than inside anoptimisticFnreducer
- Confirm the optimistic atom exists or is missing. Open
packages/react/src/api/atoms.tsxand check for<thing>OptimisticAtom = Atom.family(scopeId => Atom.optimistic(<thing>Atom(scopeId))). If a sibling resource (sources, secrets, policies) has the optimistic wrapper and this one doesn't, the bug is the missing wrapper plus the hand-rolled substitute. - Check for grandfathered code.
usePendingSources,useSourcesWithPending,useConnectionsWithPendingRemovals, andusePendingConnectionRemovalsinpackages/react/src/api/optimistic.tsxare legacy. New code should not extend them. Their continued existence is not a finding by itself; new consumers or new entries inPendingResourceare.
When the trace cannot resolve with the files at hand, drop the finding.
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 · 175 lines · 102 tokens per session scan A e2c56533f48a
wrdn-effect-atom-optimistic is a skill published in the GitHub repository UsefulSoftwareCo/executor (4,297 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 2,628 once invoked, about $0.0004 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
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
review-system-design
Review a system design someone else provided - screenshot, drawio, Mermaid, slides, doc, or IaC - by extracting it into a confirmed fact sheet, then scoring it on the nine axes.
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
react-patterns
React 19 performance patterns and composition architecture for Vite + Cloudflare projects. 50+ rules ranked by impact — eliminating waterfalls, bundle optimisation, re-render prevention, composition over boolean props, server/client boundaries, and React 19 APIs. Use when writing, reviewing, or refactoring React…
review-ticket
Review a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.
common-feedback-reporter
Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.