pipefy-process-impact

pipefy-process-impact is a skill for Claude Code from pipefy/ai-toolkit. It costs 103 tokens per session (1,784 once invoked), scanned A, original, Apache-2.0.

A guided method for estimating whether automating a business process or using an AI agent would save time. It focuses on one repetitive step and calculates the likely return from changing it.

In plain words
What is it for?
Use it to choose where to start automating, estimate time returned, assess return on investment, or prepare a brief business case. It can read an existing Pipefy process when the user names one.
Why use it?
It avoids broad automation plans without evidence by starting with the highest-volume manual step. It helps turn a vague automation idea into a short internal justification.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pipefy plugin — 19 skills, 2 commands, 1 MCP server shipped together

Good fit Use it to choose where to start automating, estimate time returned, assess return on investment, or prepare a brief business case. It can read an existing Pipefy process when the user names one.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pipefy/ai-toolkit/pipefy-process-impact
Install

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.

Any agent
npx skills add pipefy/ai-toolkit --skill pipefy-process-impact
Clone the repo
git clone --depth 1 https://github.com/pipefy/ai-toolkit

Made for: Claude Code.

Or install pipefy, the plugin that ships this one along with the rest of its 19 skills, 2 commands, 1 MCP server.

Wrote 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.

agentmods badge for pipefy-process-impact

README.md
[![agentmods](https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-process-impact/github.svg)](https://agentmods.dev/skills/pipefy/ai-toolkit/pipefy-process-impact)
Your own site
<a href="https://agentmods.dev/skills/pipefy/ai-toolkit/pipefy-process-impact"><img src="https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-process-impact/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.

agentmods 80×15 button for pipefy-process-impact

Your own site · 80×15
<a href="https://agentmods.dev/skills/pipefy/ai-toolkit/pipefy-process-impact"><img src="https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-process-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00103 $0.01784
Opus 5.5 $0.00041 $0.00714
Sonnet 5.5 $0.00021 $0.00357
Haiku 4.5 $0.00010 $0.00178

Measured 11d ago against content hash e500d06f5ff6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pipefy-process-impact 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 11d 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.

skills/process-impact/pipefy-process-impact/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Process impact

Help the user find the one step in their process where an automation or an AI agent returns the most time, and show the arithmetic. One hop, one formula, one question per turn. The next hop comes after they have the first number.

Read the MCP reference or CLI reference only when the user names a pipe, and only for the reads listed there.

When to use

  • "Is it worth automating X?" / "Where do I start?" / "What is the ROI?" / "How much time does this give back?"
  • "Help me justify this internally."
  • The user wants more than the Impact: line that pipefy-process-design or pipefy-process-intelligence already emitted.

Not for designing a process (pipefy-process-design), a full pipe diagnosis or implementation (pipefy-process-intelligence), building the step (pipefy-building, then the domain skill), or finding what a change breaks elsewhere.

How to answer

  1. Pick the hop. From the conversation, name the one manual, repetitive step with the best return: a move someone does by hand, a triage, a copy-paste, a chase. With several candidates, take the one with the most cases per week. Do not walk the whole process.
  2. Check coverage when a pipe is named. Run the reads in the reference: get_pipe, get_automations, get_ai_agents, then get_ai_agent for each active agent. If an active automation or agent already does the hop, say so, size that coverage, and move to the next uncovered hop, restating what the agent or rule already does there. Do not propose a second one. With no pipe in view, say coverage was not checked instead of claiming nothing covers the hop. cards_count is what sits in a phase now, not volume or duration, and get_cards selects no dates; when the answer needs time, use the timed card read under Measuring.
  3. Show the arithmetic, with the user's numbers or the gaps named:
hours returned per week ≈ minutes per case × cases per week / 60
cost avoided per week ≈ hours returned per week × hourly cost   (only if the user gave an hourly cost)

Read the full file on GitHub · 92 lines

Files

What ships with it

2 files 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.

Changes

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.

  1. 11d ago First seen · 92 lines · 103 tokens per session scan A e500d06f5ff6

Subscribe to this mod's changes

pipefy-process-impact is a skill published in the GitHub repository pipefy/ai-toolkit (50 stars, last pushed yesterday), licensed Apache-2.0. It adds 103 tokens to every session and 1,784 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-10-07.