pipefy-attachments

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

A file-upload guide for adding one local file or web-hosted file to a Pipefy card or table record attachment field.

In plain words
What is it for?
It helps attach files using a file path, an HTTPS URL, or Pipefy's temporary upload link process.
Why use it?
It explains which upload method works when the server can or cannot read the file, including large files and sandbox-created files.

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 It helps attach files using a file path, an HTTPS URL, or Pipefy's temporary upload link process.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/pipefy/ai-toolkit/pipefy-attachments"><img src="https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-attachments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,213 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.00046 $0.01213
Opus 5.5 $0.00018 $0.00485
Sonnet 5.5 $0.00009 $0.00243
Haiku 4.5 $0.00005 $0.00121

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

Security

Grade A, and why

pipefy-attachments 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 21d 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-attachments/SKILL.md · 135 lines

How it starts

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

Attachments

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

Upload one file at a time to a card or table-record attachment field. The upload goes through Pipefy's presigned URL flow (request URL, S3 PUT, then field update).


When to use

  • The user says "attach this file to card X" or "upload to the documents field on record Y".
  • Pick the source by where the bytes actually are. Use the source rules for your chosen surface.

Do not use this skill for:

  • Reading or listing existing attachments. There is no list/download tool in this skill scope. Cards and table records expose their attachments through the regular card/record fetch tools.
  • Bulk uploads. One file per call; iterate at the agent layer.

Prerequisites

  • A Pipefy organization_id. Find it via get_organization or get_pipe.
  • A target card_id or table_record_id.
  • The attachment field's slug (the human-readable id like document_upload, not the field's uuid). Find it on the card or table record fetch tools.
  • Exactly one file source accessible to the chosen upload surface.

Tools needed

Operation Read-only
upload_attachment_to_card No
upload_attachment_to_table_record No
create_attachment_presigned_url No

Steps

Upload a local file to a card

file_name is inferred from the source basename when omitted, so callers usually only pass the four IDs and the source.

Operation arguments:

upload_attachment_to_card(organization_id=42, card_id=1234, field_id=document_upload, file_path=~/report.pdf)

Upload from a URL

upload_attachment_to_card(organization_id=42, card_id=1234, field_id=document_upload, file_url=https://example.com/report.pdf)

When the URL has no filename in its path (e.g. .../download?id=1), pass file_name explicitly so Pipefy stores it under a real name.

Read the full file on GitHub · 135 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. 21d ago Changed · -91 lines · -20 tokens per session 877c4fba3088
  2. 1mo ago First seen · 226 lines · 66 tokens per session scan A bcb85ecdb3cd

Subscribe to this mod's changes

pipefy-attachments is a skill published in the GitHub repository pipefy/ai-toolkit (51 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 1,213 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.