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 pipefy/ai-toolkit --skill pipefy-buildinggit clone --depth 1 https://github.com/pipefy/ai-toolkitWrote 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/pipefy/ai-toolkit/pipefy-building)<a href="https://agentmods.dev/skills/pipefy/ai-toolkit/pipefy-building"><img src="https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-building/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/pipefy/ai-toolkit/pipefy-building"><img src="https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-building.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.00113 | $0.00665 |
| Opus 5.5 | $0.00045 | $0.00266 |
| Sonnet 5.5 | $0.00023 | $0.00133 |
| Haiku 4.5 | $0.00011 | $0.00067 |
Grade A, and why
pipefy-building 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipefy Building (router)
Maps what the user wants to which domain skill to read. It does not teach create/update workflows — open the linked skill for that.
If the user already has a building skill or a detailed build prompt/spec, use that for how to build; use this skill for which Pipefy skill to load.
When the user wants X → read skill Y
| User intent (examples) | Read |
|---|---|
| Design / architecture / "help me structure this process" | pipefy-process-design (consulting only) |
| Impact / ROI / "is this change worth it?" / justify internally | pipefy-process-impact (consulting; do not implement from there) |
| Pipes, phases, fields, labels, cards, field conditions | pipefy-pipes-and-cards |
| Traditional or AI automations (if/then, prompt-driven rules) | pipefy-automations |
| Conversational AI agents and behaviors | pipefy-ai-agents |
| External integration / integrate with Slack, Gmail, Sheets, or another app | pipefy-ipaas |
| Portals, pages, elements, sub-portals | pipefy-portal-setup |
| Members, email templates, inbox email, webhooks | pipefy-members-email-webhooks |
| Database tables and records | pipefy-database-tables |
| Pipe/card relations | pipefy-relations |
| Reports and exports | pipefy-reports |
| Logs, usage, credits, job exports | pipefy-observability |
| First-time toolkit setup | pipefy-toolkit-setup |
Do not re-teach domain workflows here — open the linked skill.
Product limits live in domain skills
Hard stops and quirks (phase connections UI-only, email template create/edit UI-only, incompatible automation event×action pairs, no automation action applies a label, verify-after-write, AI consent) are documented in the domain skills above; follow those contracts after routing.
See also
pipefy-process-design— consulting when the ask is design, not build.pipefy-process-impactfor consulting when the ask is impact, ROI, or justification, not build.- plugins/pipefy/README.md — full catalog.
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.
- 5d ago Changed e82909733cc2
- 19d ago Changed · +2 lines cbb1b0c456f0
- 1mo ago First seen · 51 lines · 113 tokens per session scan A 6f278285f203
pipefy-building is a skill published in the GitHub repository pipefy/ai-toolkit (51 stars, last pushed 2d ago), licensed Apache-2.0. It adds 113 tokens to every session and 665 once invoked, about $0.0005 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
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-init
Bootstrapping new Atmos projects with atmos init: built-in template catalog, differences from atmos scaffold generate, project record, and update-safe 3-way merge.
atmos-workflows
Workflow automation: native step types, multi-step workflows, parallel/matrix/wait/container/emulator steps, when: conditions (CEL), require/assert preconditions, output steps, retries, dependencies, and cross-component orchestration.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
atmos-imports
Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts.
squads-cli
Squads CLI — operate your squads through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.