pipefy-portal-setup

pipefy-portal-setup is a skill for Claude Code from pipefy/ai-toolkit. It costs 52 tokens per session (4,333 once invoked), scanned A, original, Apache-2.0.

A toolkit for configuring Pipefy portals, which are published company hubs containing pages, forms, links, and connected sub-portals.

In plain words
What is it for?
Use it to create or list portals, add pages and elements, connect sub-portals, and publish or unpublish them.
Why use it?
It helps organize how people enter and navigate Pipefy services without mixing portal setup with workflow or card management.

Skill for Claude Code

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

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

Good fit Use it to create or list portals, add pages and elements, connect sub-portals, and publish or unpublish them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pipefy/ai-toolkit/pipefy-portal-setup
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-portal-setup
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 18 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-portal-setup

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

agentmods 80×15 button for pipefy-portal-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/pipefy/ai-toolkit/pipefy-portal-setup"><img src="https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-portal-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,333 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
  • Socket pass 7 Oct 2026
  • Snyk pass 7 Oct 2026
How audits are shown
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.00052 $0.04333
Opus 5.5 $0.00021 $0.01733
Sonnet 5.5 $0.00010 $0.00867
Haiku 4.5 $0.00005 $0.00433

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

Security

Grade A, and why

pipefy-portal-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 14d 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.

plugins/pipefy/skills/pipefy-portal-setup/SKILL.md · 299 lines

How it starts

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

Portal setup

MCP clients: read references/mcp.md. CLI users: read references/cli.md. Examples below describe shared operation arguments.

Configure an organization's Pipefy portal: bootstrap the main hub, add pages and widgets, wire and publish sub-portals (Interfaces GraphQL + internal_api for sub-portal wiring).

Deep reference: docs/mcp/tools/portal.md. Parity matrix: docs/parity.md. Env vars: docs/config.md.


When to use

  • "Create our company portal", "list portals for org X", "publish a sub-portal".
  • Add or change portal pages, layout, or page elements (forms, link, etc.).
  • Attach, publish, unpublish, or delete sub-portals on the main portal.

Do not use for:

  • Pipes, phases, cards, or automations — see pipefy-pipes-and-cards, pipefy-automations.
  • Raw GraphQL when a portal tool exists — prefer the tools below.
  • Bootstrapping a portal via undocumented createInterface GraphQL — always use create_portal.

Prerequisites

  • Organization id: UUID or numeric org id from the organization lookup or the Pipefy URL (examples below use fictional 123456789 per fixture_ids.py). SDK resolves numeric ids before Interfaces calls. The org you pass to list_portals / create_portal must be the same org your token can write on.
  • Portal writes: token needs create_portal and/or manage_portals on that org. Many service accounts only have pipe/card scope on their default org → PERMISSION_DENIED on portal mutations even when reads succeed elsewhere.
  • One main portal per org — create_portal is idempotent (second call returns the same portal UUID).

Confirm access before writes

Read the full file on GitHub · 299 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. 14d ago Changed · +3 lines 9a407f058be4
  2. 17d ago Changed · -42 lines · -5 tokens per session f5ad4fdb90fc
  3. 1mo ago First seen · 338 lines · 57 tokens per session scan A ffb95c012b6f

Subscribe to this mod's changes

pipefy-portal-setup is a skill published in the GitHub repository pipefy/ai-toolkit (51 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 4,333 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-30.

Related

Other skills, from other repositories