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/pipefy/ai-toolkit/pipefy-buildingnpx 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.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.00113 | $0.00778 |
| Opus 5 | $0.00056 | $0.00389 |
| Sonnet 5 | $0.00023 | $0.00156 |
| Haiku 4.5 | $0.00011 | $0.00078 |
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 — 51 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) |
| 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.
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 First seen · 51 lines · 113 tokens per session scan A 6f278285f203
pipefy-building is a skill published in the GitHub repository pipefy/ai-toolkit (45 stars, last pushed today), licensed Apache-2.0. It adds 113 tokens to every session and 778 once invoked, about $0.0006 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
using-agent-skills
Meta-skill for selecting and applying the right skill for any task. Use when starting a task and unsure which skill to apply, or when coordinating multiple skills for a complex workflow. This is the routing brain for the entire skill set. WARNING: load this skill on-demand only — never pin it as always-active. Agent…
bug-triage
Triage bugs reported in chat/issues, search for duplicates, file or update GitHub issues with full context, and push fix PRs.
ao-desktop-dev
Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually…
using-ao
Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, spawning workers, or managing AO sessions in an AO workspace.
compare-flights
Unified flight comparison across cash (Duffel, Ignav), award (seats.aero), and portal (Chase, Amex) sources in parallel. Outputs one table with transfer partner optimization and recommendations.
trip-calculator
Cash vs points trip cost comparison. Factors in transfer ratios, taxes, fees, CPP valuations, and opportunity cost to recommend the best redemption strategy for flights and hotels.