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 skills add JohnWayneeee/ai-agent-skills --skill workflow-node-setupgit clone --depth 1 https://github.com/JohnWayneeee/ai-agent-skillsWrote 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/johnwayneeee/ai-agent-skills/workflow-node-setup)<a href="https://agentmods.dev/skills/johnwayneeee/ai-agent-skills/workflow-node-setup"><img src="https://agentmods.dev/badge/skills/johnwayneeee/ai-agent-skills/workflow-node-setup/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/johnwayneeee/ai-agent-skills/workflow-node-setup"><img src="https://agentmods.dev/badge/skills/johnwayneeee/ai-agent-skills/workflow-node-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.01251 |
| Opus 5.5 | $0.00024 | $0.00500 |
| Sonnet 5.5 | $0.00012 | $0.00250 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
workflow-node-setup 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Node Setup
Use this skill to tune React Flow workflow nodes without breaking React Flow semantics or the existing canvas interaction model.
Workflow
- Inspect the current node, shared helpers, and flow model before editing.
- Prefer shared project primitives over custom local handle styling.
- Keep React Flow ids synchronized. Every edge
sourceHandleandtargetHandlemust match an actual renderedHandleid. React Flow error#008means the edge references a missing handle. - Make visual changes in the narrowest place:
- Node content/layout belongs in the node component.
- Node dimensions, positions, edge handle ids, and edge visual style belong in the flow model.
- Canvas behavior belongs in the canvas component.
- Verify with both static checks and browser sanity checks before finishing.
Handles
- Use a shared
WorkflowHandlecomponent for standard handles when available. Do not hand-rollHandlestyling unless a node truly needs a different visual system. - For multi-channel nodes, render multiple handles with distinct ids:
<WorkflowHandle
id="source-preview-test-case"
type="source"
position="right"
style={{ top: 85 }}
/>
<WorkflowHandle
id="source-style"
type="source"
position="right"
style={{ top: 108 }}
/>
- Keep handles outside clipped content where possible. Root node should generally stay
relativeand not clip handles; use an inner shell for roundedoverflow-hidden. - For incoming edges, preserve
target-leftunless the product explicitly needs multiple target channels. - Align handles to meaningful content rows, but keep ids stable after edges point to them.
Edges
- Use explicit
sourceHandleandtargetHandlein edge definitions. - For muted dashed connections, use React Flow edge style:
const WORKFLOW_EDGE_STYLE = {
stroke: "rgba(145, 147, 151, 0.72)",
strokeDasharray: "9 9",
strokeWidth: 2,
};
- Remove
markerEndwhen the design calls for plain dashed lines without arrows. - If only one node needs a different edge style, create a separate edge style constant instead of changing all edges.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 134 lines · 59 tokens per session scan A e0d590897fee
workflow-node-setup is a skill published in the GitHub repository JohnWayneeee/ai-agent-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 1,251 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-31.
Other skills, from other repositories
raycast
Build Raycast extensions with React and TypeScript, create Script Commands, and troubleshoot URL schemes and extension execution on macOS.
graphql-client
Build Apollo Client or urql queries and mutations, manage cache behavior, and handle authentication and errors.
algolia-search
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning.
genpage
Creates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9. Orchestrates specialist agents for planning, entity creation, and code generation. Use it when user asks to build, retrieve, or update a page in an existing Microsoft Power Apps model-driven…
add-localization
Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro Power Pages site.
pcf
Builds, tests, diagnoses, upgrades, deploys and verifies Power Apps component framework (PCF) code components for model-driven apps and Power Pages — field and dataset controls, standard and virtual (React) — from Microsoft-maintained templates and recipes pinned to a tested version matrix. Runs quality gates…